We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug A user on Discord has reported that using studio to select an alternate layout on their Bakeneko60 Go, saving, and then resetting/waking from sleep results in incorrect bindings/keys in their bottom row. Original Discord message: https://discord.com/channels/719497620560543766/719909884769992755/1298114176807473204
The following details are copied from my work with them to help diagnose.
To Reproduce Steps to reproduce the behavior:
Expected behavior The layout selected in ZMK Studio will be properly loaded on startup and used until changed.
Screenshots N/A
Environment (please complete the following information):
I've sent them a recent firmware for their keyboard with some manually added logging statements added, waiting for them to report results of testing.
The text was updated successfully, but these errors were encountered:
petejohanson
Successfully merging a pull request may close this issue.
Describe the bug
A user on Discord has reported that using studio to select an alternate layout on their Bakeneko60 Go, saving, and then resetting/waking from sleep results in incorrect bindings/keys in their bottom row. Original Discord message: https://discord.com/channels/719497620560543766/719909884769992755/1298114176807473204
The following details are copied from my work with them to help diagnose.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The layout selected in ZMK Studio will be properly loaded on startup and used until changed.
Screenshots
N/A
Environment (please complete the following information):
I've sent them a recent firmware for their keyboard with some manually added logging statements added, waiting for them to report results of testing.
The text was updated successfully, but these errors were encountered: