-
-
Notifications
You must be signed in to change notification settings - Fork 39.9k
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
[Bug] Keycodes get shifted by one after #9940, that breaks correct indication in VIA #11157
Comments
Isn't this more a VIA problem? If VIA development doesn't keep up with the changes in QMK it's not this projects problem. |
It is not that simple. This bug is not fixable on VIA side. The problem is that after this breaking PR got accepted, there are two conflicting sets of QMK keycodes - old one, which is still running on countless devices all over the world, and new one, in those keebs that got their firmware flashed/updated recently. The VIA API does not have a way to know which version of QMK a keyboard runs, so VIA can't comply with this change. |
This only affects user builds of firmware using QMK master. I haven't built/uploaded new firmware to the VIA website after this breaking change, and I can unbreak it in those builds (doing one now, actually). |
This is fixed now. |
Change in #9940 causes keycodes after MIDI block in quantum_keycodes.h to shift by 1, which causes VIA to show wrong labels for certain keycodes, like RGB lighting controls. The aforementioned change is in the code block that is defined even when MIDI is disabled, so it influences all devices, even those that do not use MIDI.
The text was updated successfully, but these errors were encountered: