In the emulator, if I want to get the '[' character, I hit 'Alt' then 'f'. In my custom view, this invokes two onKeyDown callbacks for keycodes 57 (alt) then 34 (f). So I had been happily building my app to handle 57 then 34 as a '[' . Now I look at the hardware keyboard on a droid and 'Alt' 'f' is '$' . And on the LG Eve, most of the special 'alt' keys are yet another combination. Yikes. So I must be doing this wrong. Detecting the device and then mapping the keys differently for each different keyboard just can't be right. But I can't find another way to get the correct keys into my system.
Can anyone point me in the right direction? Thank you.
-- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
