Open GlassBricks opened 1 year ago
Strange; this should have been fixed by #17282, which is present in 0.20.0. (Before that change the behavior of OSM()
on a layer behind LT()
was broken, unless you first held LT()
until the end of its tapping term, and then released it after releasing OSM()
.)
After some more investigation (setting timeouts to be super long), I found this issue only occurs when multiple OSM keys are pressed (e.g. OSM Ctrl + Shift); Pressing multiple OSM keys works with MO()
but not LT()
... and with HOLD_ON_OTHER_KEY_PRESS
Even more investigation later, it's only HOLD_ON_OTHER_KEY_PRESS that causes the issue with multiple OSM keys. This doesn't have to do with MO vs LT; it just happens that I only turned on HOLD_ON_OTHER_KEY_PRESS after LT.
Side note: this issue is getting modified a lot. Should I close this issue and open another one?
Can you describe the exact sequence of key presses and releases that triggers the problem? I can't reproduce it here with LT(1, KC_CAPS)
and OSM(MOD_RGUI)
, OSM(MOD_RCTL)
on that layer; however, I'm also using the code from the develop
branch (as of yesterday), so maybe there is some difference due to that.
I have the same issue. My usecase is that I have my sticky home row mods on a momentary layer. They are sticky, so I can press the layer key, two modifiers, release everything and then press a key from my base layer resulting in e.g. cmd + ctrl + q.
HOLD_ON_OTHER_KEY_PRESS
breaks this
My current workaround is to use HOLD_ON_OTHER_KEY_PRESS_PER_KEY
Describe the Bug
Summary after some edits:
When HOLD_ON_OTHER_KEY_PRESS is on, pressing multiple OSM keys together (on another layer) loses the OSM behavior. This happens with the layer activated either through MO or LT.
Previous (outdated) description:
Using Elite-Pi controllers on a split keyboard.
Keyboard Used
splitkb kyria rev3
Link to product page (if applicable)
No response
Operating System
No response
qmk doctor Output
Is AutoHotKey / Karabiner installed
Other keyboard-related software installed
No response
Additional Context
No response