-
-
Notifications
You must be signed in to change notification settings - Fork 39.9k
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
Combo TAP_CODE_DELAY
and clear_weak_mods
#15866
Conversation
Some software don't like key press and release events too close to each other, so a delay is needed after dumping the key buffer in combo processing.
Before, weak mods from combos could leak to the next key press if pressed too fast.
Why does "some software" have to suck so bad... I hate having |
Needs some work still. If a mod-tap or similar is part of a combo, the delay is applied twice after releasing the key (once in combo processing, once in the |
Is this ready to go, as is? |
Yeah, should be good to go, haven't had problems with it. |
Signed-off-by: Dušan <[email protected]>
Signed-off-by: Dušan <[email protected]>
Description
TAP_CODE_DELAY
: Some software (e.g. some games) don't like key press and release events too close to each other, so a delay is needed after dumping the key buffer in combo processing.clear_weak_mods
: Before, weak mods from combos could leak to the next key press if pressed too fast.Types of Changes
Checklist