Hey all,
I''m working on a GUI application for Windows Mobile and I'm having trouble detectomg input on devices with QWERTY keyboards (HTC and Samsung models). Two questions:
A: QWERTY input works "under the hood" in standard windows gui components, but in this application we create own GUI and thus we directly handle the basic Form.OnKeyPressed and Form.OnKeyDown events. The data sent to the event handlers don't seem to contain correctly mapped key codes for QWERTY keys with or without modifiers...
What is the "canon" way of detecting what the QWERTY keys actually "intend" to send - ie. intended character taking into consideration pressed modifier keys such as fn, caps, shift etc.
B: Is there any straight forward way of detecting whether the device has QWERTY capability and/or is in "QWERTY mode"* (ie. keyboard slid out on slide models?)
Regards,
Thomas Kjeldahl Nilsson
More...
View All Our Microsoft Related Feeds
I''m working on a GUI application for Windows Mobile and I'm having trouble detectomg input on devices with QWERTY keyboards (HTC and Samsung models). Two questions:
A: QWERTY input works "under the hood" in standard windows gui components, but in this application we create own GUI and thus we directly handle the basic Form.OnKeyPressed and Form.OnKeyDown events. The data sent to the event handlers don't seem to contain correctly mapped key codes for QWERTY keys with or without modifiers...
What is the "canon" way of detecting what the QWERTY keys actually "intend" to send - ie. intended character taking into consideration pressed modifier keys such as fn, caps, shift etc.
B: Is there any straight forward way of detecting whether the device has QWERTY capability and/or is in "QWERTY mode"* (ie. keyboard slid out on slide models?)
Regards,
Thomas Kjeldahl Nilsson
More...
View All Our Microsoft Related Feeds
