You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I need to differentiate between the number(key) pad to the right of the arrow keys, and the numbers across the top of the keyboard.
Describe the solution you'd like
A quick and dirty solution would be for KeyEvent to also have a scancode attached allowing the developer to handle specific scan codes. A more elegant solution would be for KeyEvent to hold a keypad(key_1) enum including /*-+[enter] as well.
Describe alternatives you've considered if any
I've dumped events and currently there is no difference between KeyCode::char('1') originating at either spot on the keyboard.
Additional context
KeyEvent::KeypadBegin could be deprecated with this change.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I need to differentiate between the number(key) pad to the right of the arrow keys, and the numbers across the top of the keyboard.
Describe the solution you'd like
A quick and dirty solution would be for
KeyEvent
to also have ascancode
attached allowing the developer to handle specific scan codes. A more elegant solution would be for KeyEvent to hold akeypad(key_1)
enum including/*-+[enter]
as well.Describe alternatives you've considered if any
I've dumped events and currently there is no difference between
KeyCode::char('1')
originating at either spot on the keyboard.Additional context
KeyEvent::KeypadBegin could be deprecated with this change.
The text was updated successfully, but these errors were encountered: