From b70d76d45cff0bd3997c185bc43f964f5e74dc1e Mon Sep 17 00:00:00 2001 From: rillian Date: Fri, 22 Feb 2013 18:28:12 +0000 Subject: [PATCH] Added a comment: Re: no keybourd events on Galaxy Tab 10.1 --- ...ment_11_230d3c169c713f613b9d607d84ce5092._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/design/assistant/blog/day_195__real_android_app/comment_11_230d3c169c713f613b9d607d84ce5092._comment diff --git a/doc/design/assistant/blog/day_195__real_android_app/comment_11_230d3c169c713f613b9d607d84ce5092._comment b/doc/design/assistant/blog/day_195__real_android_app/comment_11_230d3c169c713f613b9d607d84ce5092._comment new file mode 100644 index 0000000000..a984dd339a --- /dev/null +++ b/doc/design/assistant/blog/day_195__real_android_app/comment_11_230d3c169c713f613b9d607d84ce5092._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="rillian" + ip="64.213.70.194" + subject="Re: no keybourd events on Galaxy Tab 10.1" + date="2013-02-22T18:28:11Z" + content=""" +KBOX has the same input problem so you didn't break anything with your changes. + +I was testing with the soft keyboard. Turns out the spacebar and number keys on the soft keyboard work, as well as return, just not the alphabetic keys. + +Trying on a hardware keyboard (Samsung docking station) is similar. Space, Enter and numbers work, but not letters. There's some additional confusion about shift state, where it gets confused and reports shifted digits from the hardware keys when the soft keyboard is in some shift states. E.g. switching the soft keyboard to numeric mode results in shift-digits (punctuation) from the hardware numeric keys. +"""]]