Qmk_firmware: NO_ACTION_TAPPING disables layers
I was just playing around for fun, because I'm probably going to use taps at one point. But defining NO_ACTION_TAPPING disables the layer switching. Even with MO
jandk
All 4 comments
That's odd.
I can confirm that MO is disabled, but .... TG is not.
Oh, okay. MO is technically ACTION_LAYER_TAP((layer), OP_ON_OFF). So, we'd need to more finely ifdef it...
drashna
on 30 Apr 2019
Good to know, thought I went crazy for a minute 馃槉
jandk
on 30 Apr 2019
I mean, crazy is always a possibility, but this is definitely an unintended effect.
I'll see about fixing this, if i can.
drashna
on 30 Apr 2019
😄1
I was running into this issue as well, Clueboard 66 Hotswap prototype (atmega32u4), NO_ACTION_TAPPING was defined by default for this keyboard, so I had to undef it to enable my MO() layer tapping as well as LT() layer switching.
thinkv
on 8 May 2019
👍2
Was this page helpful?
0 / 5 - 0 ratings
Related issues
BenRoe
路
3Comments
helluvamatt
路
4Comments
ghost
路
3Comments
MarkuBu
路
3Comments
matz-e
路
4Comments
Most helpful comment
I was running into this issue as well, Clueboard 66 Hotswap prototype (atmega32u4), NO_ACTION_TAPPING was defined by default for this keyboard, so I had to undef it to enable my MO() layer tapping as well as LT() layer switching.