Flashing Mods

[urob]

I am not sure whether this is per design or a bug, but I am experiencing an issue with the bilateral combination setting. Despite it being turned on, the modifier code still seems to register for same-handed combinations. But instead of being sent together with the next key code, it is sent by itself.

Describe the Bug

Example (using colemak):

1. Press and hold LGUI_T(KC_A) longer than TAPPING_TERM
2. Press any other left-hand key, for example KC_R

This results in the following sequence of key strokes:

1. KC_LGUI
2. KC_A
3. KC_R

Note that the modifier is not sent together with the next key, instead it is sent by "itself" (triggered upon pressing the 2nd key). Accordingly, this issue does not matter for modifiers which do not do anything by themselves (shift, control), but for Alt and in particular for Gui, it has unintended effects on Windows 10. E.g., the above sequence will result in the windows start menu being opened and "AR" being typed into the search bar.

System Information

• Keyboard:
  • Revision (if applicable): Katana60 rev2
• Operating system: Windows 10
• AVR GCC version: 8.4.0
• ARM GCC version: 8.3.1 20190703 (release) [gcc-8-branch revision 273027]
• QMK Firmware version: 0.12.50 (merged with the Oct 26, 2020 version of your bilateral-combinations branch)
• Any keyboard related software installed?
  • [ ] AutoHotKey
  • [ ] Karabiner
  • [x] Other: WinCompose v0.9.6 (issue persists when disabling the software)

[urob]

Adding my tap-hold configuration:

#define TAPPING_TERM_PER_KEY
#define IGNORE_MOD_TAP_INTERRUPT
#define TAPPING_FORCE_HOLD_PER_KEY
#define PERMISSIVE_HOLD
#define BILATERAL_COMBINATIONS
#define QMK_KEYS_PER_SCAN 4

[manna-harbour]

Thanks for the report.

Yes, there is an issue with flashing mods due to the way this is implemented. The same issue is present in retro tapping. Bindings for mod presses can be disabled in some environments, but probably not in windows.

I've added an issue to clarify the status of bilateral combinations: #29.

[sunaku]

I've attempted to fix this issue in pull request #48. Please check if it works for you, @urob.

[urob]

I've attempted to fix this issue in pull request #48. Please check if it works for you, @urob.

Thanks for fixing this! This issue was one of the last sources for HRM misfires.

Unfortunately, I can't test at the moment as I no longer have the QMK tools set up (I migrated to ZMK in the meantime).