qmk / qmk_firmware

Open-source keyboard firmware for Atmel AVR and Arm USB families
https://qmk.fm
GNU General Public License v2.0
18.28k stars 39.38k forks source link

[Bug] THe problem is back (OSM shift) #8211

Closed danielo515 closed 2 years ago

danielo515 commented 4 years ago

Hello, I want to report an odd behavior that I get with one shot modifiers from time to time. I am aware that this was a known problem before: https://github.com/tmk/tmk_keyboard/issues/67 Seems that the problem was fixed by using one shot modifiers, but my problem is precisely with one shot modifiers, so I'm not sure how related they are.

Describe the Bug

When I use the shift key as a one shot modifier some times I get two keys shifted up instead of two. It usually happens when I type fast, like when you type usual words such as ME.

System Information

Additional Context

If it helps, here is my config.h (this is the simplest one on a keyboard where the problem exists)

#define IGNORE_MOD_TAP_INTERRUPT
#define TAPPING_TERM 200

and my rules.mk

TAP_DANCE_ENABLE = yes # Enable the tap dance feature.
COMBO_ENABLE = yes
LEADER_ENABLE = yes
CONSOLE_ENABLE = no
LTO_ENABLE = yes # link time optimizations

I also have enabled combos, tap dance, leader key

drashna commented 4 years ago

Could you try disabling/uninstalling Karabiner and see if the issue is fixed. It could be an interaction between the two things that is causing this issue.

danielo515 commented 4 years ago

Sure, will try

kabuko commented 4 years ago

For me, this was an issue specifically with Karabiner and this was also the case outlined in a previous issue. I would love to hear a solution other than disabling Karabiner, but that's probably an issue to bring up with Karabiner rather than QMK. I think it's to do with the simultaneous mode handling in Karabiner.

danielo515 commented 4 years ago

I have to say that, since I have Karabiner disabled I don't have this problem anymore.

zvecr commented 2 years ago

This issue has been automatically closed because it has not had any recent activity. If this issue is still valid, re-open the issue and let us know.