Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Numpad Keycodes and Android Keycodes collides / Optimize generation of scancodes #42

Open
joBr99 opened this issue Apr 2, 2018 · 1 comment
Open

Numpad Keycodes and Android Keycodes collides / Optimize generation of scancodes #42

joBr99 opened this issue Apr 2, 2018 · 1 comment

Comments

@joBr99
Copy link

joBr99 commented Apr 2, 2018 •
edited
Loading

I've just found that my numpad is typeing chars in the english layout.
For example Numpad 7 has JavaScript KeyCode 103 (0x67), which is also the KeyCode of 'g' on my android phone.

Android is sending always 229 as KeyCode to get around this I've seen that you are mapping the unicode position of the char to the scancode. Maybe we should always use the unicode way, except for the arrow keys and similar keys.

Open for good ideas to handle that problem...
@cnlohr
Copy link
Owner

cnlohr commented Apr 2, 2018

I don't really have any input on this, I've been out of the project for so long, but if you can find a solution, please let me know and make a PR!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@cnlohr @joBr99