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

Fix the TO(n) key codes issue. #747

Merged

yoichiro merged 1 commit into main from fix-to-key-code-issue

Oct 19, 2022

Collaborator

yoichiro commented Oct 19, 2022

Fix #746

This pull request fixes the issue that the TO(n) key codes are different from them of current QMK Firmware.

See: qmk/qmk_firmware#17989


          Fix the TO(n) key codes issue.

c3f230d

Collaborator Author

yoichiro commented Oct 19, 2022 •

edited

Loading

When testing behaviors of TO(0), TO(1) and TO(2) using my Lunakey Macro keyboard, they normally work.

I built a firmware with the latest master branch of QMK Firmware. Then, I flashed it to the MCU of my keyboard.
I assigned TO(0), TO(1) and TO(2) to each layer with fixed Remap.
I pressed TO(n) key and confirmed to move to each target layout normally.
I unpluged and re-plug the USB cable from/to the keyboard, and I confirmed that each TO(n) was normally fetched from the MCU and was displayed on the Remap.

yoichiro merged commit 4b3f29f into main

yoichiro deleted the fix-to-key-code-issue branch

October 19, 2022 10:30

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

Labels

None yet