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.

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

Closed
ruddy17 opened this issue Dec 8, 2020 · 4 comments

Comments

@ruddy17
Copy link
Contributor

ruddy17 commented Dec 8, 2020

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.

@kb-elmo
Copy link
Contributor

kb-elmo commented Jan 3, 2021

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.

@ruddy17
Copy link
Contributor Author

ruddy17 commented Jan 3, 2021

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 implementation, where a keycode values assigned implicitly by their position in the list, is causing lot of problems and limits safe changes in the keycode set. Obviously #9940 shouldn't been merged, as any other PR that change the values of existing keycodes! I suggest it to be reverted and some work to be done to ensure all existing keycodes have their values stay the same between revisions.

@wilba
Copy link
Contributor

wilba commented Jan 4, 2021

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).

@drashna
Copy link
Member

drashna commented Mar 15, 2021

This is fixed now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants