-
Notifications
You must be signed in to change notification settings - Fork 73
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
Having numlock on changes keypresses in dragonfly2 0.32.0
#350
Comments
Thank you for opening this issue. I'm fairly certain I know what is causing the problem and will fix it in the next patch version. |
Thank you very much for noting this issue wasn't present in 0.31.2, @LexiconCode! I see now that the issue is related to use of the This flag is mentioned here, for instance, where the "scan code was preceded by a prefix byte having the value 0xE0 (224)". However, the scan codes for certain keys (e.g. the Up arrow key) do not have the prefix byte when retrieved via Anyway, I'll fix the problem in PR #352 by restoring the hard-coded list of extended keys of the older type. |
I think confusing is an understatement. Yuck. |
For sure. The documentation just needs to be clearer, really. A sentence or two in all relevant Remarks sections would be enough. 🤷 |
Having numlock on
Key("del")
emulates.
instead of the delete key in dragonfly20.32.0
.The same issue is not present in
0.31.2
Other keys are affected but I'll need to research.
The text was updated successfully, but these errors were encountered: