You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a macro that contains a sticky LSHIFT is run while other typing is happening, the release for the LSHIFT is either not read/ not sent, resulting in a stuck LSHIFT.
Unplugging the kb does not release the key.
This affects not only typing but the OS.
The shift key is effectively always pressed.
To release the LSHIFT, you have to either
unplug the kb, reconnect, then rerun the same macro, and allow it to finish
run a macro containing ¯o_release &kp LSHIFT
I'm connected via USB, if that makes a difference.
I'm assuming that this will happen with other modifiers as well.
Config:
The quick-release must be enabled for sticky keys.
There needs to be one keypress before the sticky key in the macro.
Bug:
When a macro that contains a sticky LSHIFT is run while other typing is happening, the release for the LSHIFT is either not read/ not sent, resulting in a stuck LSHIFT.
Unplugging the kb does not release the key.
This affects not only typing but the OS.
The shift key is effectively always pressed.
To release the LSHIFT, you have to either
¯o_release &kp LSHIFT
I'm connected via USB, if that makes a difference.
I'm assuming that this will happen with other modifiers as well.
Config:
quick-release
must be enabled for sticky keys.example typing behavior:
ststststst* sTSTSTSTSTS**tststststst
*start of sk macro
**release macro
Environment:
OS: Win10
board: Horizon
repo: https://github.com/Incblob/zmk-config-horizon
connection: USB
The text was updated successfully, but these errors were encountered: