-
Notifications
You must be signed in to change notification settings - Fork 434
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(question) how to check is_keypad in callback? #216
Comments
Hi @jayquonmarton . Sorry for taking so long to answer, life's been keeping me busy. Unfortunately you are correct, the hotkey API does not provide this functionality. You would have to implement your own hotkey handling on top of Fine grained event filtering for hotkeys (also useful for making physical-keyboard-specific hotkeys) is something I've been considering, but I don't see any clear answers. |
Would it be possible for the library to pass the The current way you specify args in the Or would it be better to filter the events by allowing the user to specify a keypad modifier in the Or perhaps both are worthwhile? |
@jayquonmarton Obviously this may not be useful to you now, but so you know and for others, you can use:
In order to specifically listen for The scancodes are as follows:
I believe hotkeys should differentiate |
I want to setup hotkeys for the numpad 1 key. In #215 (comment) ,
KeyboardEvent.is_keypad
is mentioned as a workaround. How do you check thatKeyboardEvent
property when you add hotkeys via theadd_hotkey
API? I don't see a way to access theKeyboardEvent
in theadd_hotkey
callback.Thanks
The text was updated successfully, but these errors were encountered: