-
-
Notifications
You must be signed in to change notification settings - Fork 40.1k
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
Space Cadet Shifts sends extraneous input with KC_GESC #3701
Comments
Hmm, I'm pretty sure that's because of how the two key codes work. Not sure there is a simple fix here, and it may be a bit involved to fix. |
Is there a possible workaround for this issue? |
Not that I'm aware of. |
It was mentioned that #5226 fixes this issue, but #5226 was replaced by #5277—@XScorpion2, can this issue be closed? |
Ya, this issue should be closed. I just tested it to make sure this doesn't occur with the latest code too and it all checks out. |
Thanks for reporting this! |
When typing with normal alphanumeric characters a quick shift + character sends the correct output. However, when space cadet shifts are enabled, Using either shifts for a
Shift + GESC
to access ~ outputs~)
and~(
when the keycombo is pressed quickly enough.For reference, I'm using a DZ60 with pretty vanilla firmware (no special macros or anything).
Let me know if there's any additional information needed, but I think this should be reproducible in all keyboards.
The text was updated successfully, but these errors were encountered: