-
Notifications
You must be signed in to change notification settings - Fork 105
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
Feature Request: Add support for F13-F24 keys for keybindings #436
Comments
What OS are you on? We'd like to ask you to test a build to make sure it's correct |
OS: Kubuntu 22.04.4 LTS x86_64 |
Please download a nightly build from here and check that it works, thanks https://ileonte.dev/focus-builds/Linux/nightly/focus-linux-nightly-2c2a748 |
|
Thanks, will fix and will send you another build later |
Sorry for taking this long, had a busy 2 weeks. When you were testing this, did the keys F1-F16 work, or was it only F1-F12? When you have a moment, please try the latest build from here when it builds https://ileonte.dev/focus-builds/Linux/nightly/ |
Tested it again on focus-linux-nightly-45b31c2, F1-F12 work fine, F13-F24 do not. |
I was testing the same feature in raylib, keycodes for f13-f24 are the following: |
This is what we have for those keys focus/modules/Linux_Display/X11.jai Line 419 in 0eb0b86
|
Someone with Linux knowledge will need to look at this. It's hard to debug this without a proper keyboard and a proper OS. Please follow up on Discord if it gets neglected for too long. |
I'm looking at fixing this but I don't have a keyboard that can generate F13-F24 so I'm going to have to make some guesses here. Before I do that, @DSVDiniz can I please ask you to test if running with the XCB backend makes any difference for you? From a terminal run:
(you may need to install some extra packages on Ubuntu 22.04, if you need any help with that let me know) |
Looks like this is getting delayed |
I use a keyboard with custom macro keys that use the old F13-F24 keys, maybe I'm just an outlier but this would help me out greatly.
The text was updated successfully, but these errors were encountered: