On my Keychron K3 there is a key combination that deactivates the light-pattern-changing key. Now, if I accidentally hit it, it just flashes a couple of times and goes back to the setting I had it on. Check your manual.
Had the same issue, instead of no-op did "momentary layer toggle" - the key still switches the layer, but only while you holding it. That gives time to re-adjust.
I use a QMK keyboard, and wrote some code for the firmware that would enforce this in the keyboard itself. "Naughty" combinations like you listed would just NO_OP instead of emitting a scan code.
It was frustrating as hell. Which, I guess is the point at first. But I got tired of it faster than I learned to balance the key presses.
I wonder if just a small beep or other subtle signal would work? Allow the wrong combo, but give the typist some feedback.
You could first check via `xev` whether the key presses actually arrive in software. For me they did, but my desktop environment didn't adjust the brightness if an `XF86MonBrightnessUp` event fired.
You could delay the display of the color pattern until the user has stopped keying for a second or so. That way, the shoulder surfer would not get incremental versions to work from, unless the user types really s l o w l y.
Is that what's happening? My kinesis advantage (plugged into a Mac) sometimes gets stuck modifier keys and only unplugging it and plugging it back in fixes it. Seems worse than just dropping some keyup events, because it doesn't get unstuck if I hit the modifier key again.
reply