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

Hexgears Gemini: ENTER key is mapped to key 70, but actual key is 71 #153

Open
elafargue opened this issue Nov 7, 2019 · 2 comments
Open

Comments

@elafargue
Copy link

On a new Gemini keyboard when configuring animations ,the configurator maps the Enter key to id 70 which is not correct, it should be 71.

How to reproduce: create a single color led layout, flash the keyboard. The Enter key will be unlit.
Fixing: edit the animation manually, replace the mapping at 70 by 71, and it works fine.

@al45tair
Copy link

FWIW, I can't get the manual edit to work. When I change the P[70] to P[71] in the "frames" array in the JSON, the result is all of the lighting on the keyboard turns off. Perhaps I'm missing something?

@elafargue
Copy link
Author

Yes, there are apparently other bugs on top of this, but as long as you just define a static LED mapping, change "70" to "71" and you don't go back to the key mapping screen, then it should work. But if you get fancy after this and try to build a complex mapping, in my experience it breaks down completely and often the keyboard firmware will remain stuck in bootloader mode, or require a press on the reset button to upload a new FW...

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

No branches or pull requests

2 participants