- From: <bugzilla@jessica.w3.org>
- Date: Tue, 26 Feb 2013 05:41:45 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21083
Gary Kacmarcik <garykac@google.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |garykac@google.com
--- Comment #3 from Gary Kacmarcik <garykac@google.com> ---
I'm not sure it makes sense to maps these values to 'key' or 'char'.
The documentation states:
"Key codes typically correspond one-to-one with individual keys on an input
device. Many keys and key combinations serve quite different functions on
different input devices so care must be taken when interpreting them. Always
use the KeyCharacterMap associated with the input device when mapping keys to
characters."
This sounds more like a 'code' value and some of the names (like
KEYCODE_ZENKAKU_HANKAKU and KEYCODE_KATAKANA_HIRAGANA) are consistent with this
interpretation.
To get a key/char, it looks like you'd need to pass the code value to the
KeyCharacterMap
(http://developer.android.com/reference/android/view/KeyCharacterMap.html)
rather than using these codes directly.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 26 February 2013 05:41:47 UTC