4 ms·
You only notice the difference when holding a key for auto repeat, which I almost never do, much less with alphabet keys.
by pfortuny 5y ago
You only notice the difference when holding a key for auto repeat, which I almost never do, much less with alphabet keys.
- toast0 5y agoYou may also notice if you're typing a word; say 'jeans' and you press the e before you release the j. On a typewritter, you must release the first key before you press another, or you get a jam. On a computer, you don't usually have to, but with this configuration, it gets tricky. If j becomes control when held, you've got to start buffering key presses when j is pressed, and only once j is released (or held long enough) can you send the key presses on. I hope you're not playing a game which uses j, because your inputs now have jitter.
- deleted 5y ago[deleted]
- rgoulter 5y ago> but with this configuration, it gets tricky. It may also be unclear what you intend if while holding 'j', you start pressing another key. The behaviour is customisable. https://docs.qmk.fm/#/tap_hold?id=tap-or-hold-decision-modes https://docs.qmk.fm/#/tap_hold?id=tap-or-hold-decision-modes > I hope you're not playing a game which uses j, because your inputs now have jitter. Well, if you've got tap-hold on the keys "ASD", then games with WASD movement will be hard to play. :) -- I have a gaming layer without the tap-hold keys, separate from the normal typing layer.