Crossover bilateral combinations for dual-hand chords and rolls #54
+64
−5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thanks to the increased typing speed made possible by PR #48, I discovered a blind spot in the bilateral combinations concept and patched it in a new optional feature called "crossover" bilateral combinations (implemented in this PR) to catch fast "rolls" that cross the left/right keyboard boundary. For example, imagine that you had Miryoku-style home row mods on the standard QWERTY layout so that typing the word "jam" involves the
RSFT_T(KC_J)
andLGUI_T(KC_A)
keys. 👉 Regular bilateral combinations would ignore this combination since the keys are located on different sides of the keyboard, thereby sendingRSFT(KC_A)
to the computer. ☝️ In contrast, crossover bilateral combinations catch this combination (if you're quick enough, according to a configurable timeout) and sendKC_J
andKC_A
to the computer, thus avoiding accidental mods.Here is the relevant portion of my
config.h
file which activates both patches to provide the best typing experience I've felt since switching to Miryoku's home row mods ~2 years ago, as detailed in Taming home row mods with Bilateral Combinations:You also need to add the following line to your
rules.mk
file to enable QMK's deferred execution facility, used by DeferMods:DEFERRED_EXEC_ENABLE = yes
Note: QMK's deferred execution feature was introduced 1 year later (on 16 November 2021 in commit 36d123e) after the latest in Miryoku's bilateral-combinations branch! So in order to try out my latest changes, you'll need to update this branch to a more recent version of mainline QMK. I've already done this (resolving merge conflicts) in a separate branch based on 0.18.6, so simply check out that branch and configure your
config.h
andrules.mk
files (as I've documented previously) to try it out.