qmk/qmk_firmware
GitHub で見る[Bug] MODS_TO_NEUTRALIZE ignored in Layer activated by Hold-Tap button
Open
#24,123 opened on 2024年7月15日
bughelp wanted
Repository metrics
- Stars
- (20,368 stars)
- PR merge metrics
- (平均マージ 20d 9h) (30d で 27 merged PRs)
説明
Describe the Bug
I have a mod-tap key in Layer 2:
MT(MOD_LGUI, KC_6)
Layer 2 is activated from a hold-tap button:
LT(MO(2), KC_ENT)
I have neutralized GUI, but with the above conditions a hold causes GUI action to trigger.
Note that if I replace the layer-activation button with a non-hold-tap one, neutralization works correctly:
MO(2)
Keyboard Used
splitkb/aurora/sweep/rev1
Link to product page (if applicable)
No response
Operating System
Windows 11
qmk doctor Output
No response
Is AutoHotKey / Karabiner installed
- AutoHotKey (Windows)
- Karabiner (macOS)
Other keyboard-related software installed
No response
Additional Context
Flags in config.h: #define QUICK_TAP_TERM 0 #define TAPPING_TERM 175 #define PERMISSIVE_HOLD #define RETRO_TAPPING #define RETRO_TAPPING_PER_KEY #define MODS_TO_NEUTRALIZE { MOD_BIT(KC_LGUI), MOD_BIT(KC_LALT) } #define DUMMY_MOD_NEUTRALIZER_KEYCODE KC_RIGHT_CTRL