Skip to content
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

[Feature request] Sequential combo 'flavor' #2260

Open
Intuos5 opened this issue Apr 7, 2024 · 1 comment
Open

[Feature request] Sequential combo 'flavor' #2260

Intuos5 opened this issue Apr 7, 2024 · 1 comment

Comments

@Intuos5
Copy link

Intuos5 commented Apr 7, 2024

By default, combos are evaluated based on whether a combination of keys is held within the timeout-ms threshold. This, however, means that the order in which the keys were pressed does not matter. I would like to request a sequential combo flavor, in which the order of the keystrokes also matters for a combo activation. This is interesting in combination with hold_taps and layer changing behaviors, because these require you to hold down a key. Pressing the next key then activates the combo, but not vice versa (e.g. key 1 followed by 2 does activate a combo, but 1 followed by 2 does not).
With homerow mods, this sequential combo could also be used to prevent certain specific accidental chorded (rolled) capitalisations, the negation of which can than enable a further reduction of require-prior-idle-ms and/ or the tapping-term-ms.

@caksoylar
Copy link
Contributor

For reference, QMK has a COMBO_MUST_PRESS_IN_ORDER_PER_COMBO option to do this: https://docs.qmk.fm/#/feature_combo?id=per-combo-timing-holding-tapping-and-key-press-order

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants