qmk/qmk_firmware

Adding combos to my keyboard messes up some mod-taps (not the same keys)

Open

#11,543 opened on 2021年1月13日

GitHub で見る
 (2 comments) (0 reactions) (0 assignees)C (43,867 forks)batch import
bughelp wanted

Repository metrics

Stars
 (20,368 stars)
PR merge metrics
 (平均マージ 20d 9h) (30d で 27 merged PRs)

説明

Hi!

I've been trying to add combos to my keyboard for accented letters (é on ER for example), so I followed the tutorial in the QMK docs, and got my combos working just fine, even those that were on the same keys as mod-taps (home row mods) thanks to the PR this article is talking about (although the problem first appeared before I merged that PR to add mod tap combos).

The problem that appeared then is some of my keys (mod-taps), but not all, started behaving strangely.

You can see in my keymap the TAB_MEH, ESC_FN, and SFT_A (all on the base layer) are far from being the only mod-taps in my keymap, but these are the only ones being affected.

What happens is that they behave erratically, sometimes working just fine, sometimes not registering, and sometimes even freezing the whole keyboard for 5 to 10 seconds (or that may be until my frustrated key mashing triggers something else...). This for either the tap or the hold role of each key.

I've tried reducing the combos to a minimum, keeping just one and having it just tap_keycode(KC_U); for example, but the same behaviour persists.

The issue seems somewhat similar to #5595, in that taking the COMBO_TERM up seems to make the issue happen a bit less, but I'm not even sure of that.

I've been trying to get help on Discord, and some very nice people have tried to help me but we couldn't find anything wrong with my keymap or config.

Any ideas what I could be doing wrong?

コントリビューターガイド