ToM / MoDK: holding Extend will briefly activate a secondary layer that was previously used.

[blankCubicle]

How to reproduce:

1. Configure CapsLock to be either Back/Extend or Mother-of-DK.
2. (optional) Enable help image, set tapModTime setting to a higher value for easier visualization.
3. Hold AltGr+Extend, then release AltGr.
4. Numpad layer will be active, release Extend to deactivate.
5. Hold Extend only to activate the default Navigation layer.

Expected result:
Navigation layer should activate right away.

Actual result:
The Numpad layer activates for a moment (exactly the time tapModTime is set to), only after that the Navigation layer will be activated. Kaomoji, coding and any other configured layers exhibit the same behavior.

[DreymaR]

I tried setting my tapModTime to a very high value as I couldn't verify your problem otherwise. But then I experience another problem: I can't activate the Extend2 (NumPad) layer anymore. Strange.

The Ext-tap layers shouldn't act the same way as hold layers. They should be active until released, as they are in reality dead keys. So they should not be subject to timers. The stickyTime timer will affect their release, but that's by design (as I found it cool that I could release different Kaomoji by timing the sequence differently).

Not sure why you'd want a tapModTime longer than 250 ms? This is the time below which a tap-or-mod key will be detected as a tap, and 1/4 s is actually quite slow for a tap. What time setting have you been using?

[blankCubicle]

I've been using 150 ms tapModTime. Maybe I could go lower, but since I press extend and the desired ext_NavEdit key at almost the same time, I'd still have to make sure it was the last active hold layer.

Tap layers/dead keys work great, are not affected and I do like the key sequences! I've been using these a lot more.

I tried setting my tapModTime to a very high value as I couldn't verify your problem otherwise. But then I experience another problem: I can't activate the Extend2 (NumPad) layer anymore. Strange.

I tried up to 5 seconds and could still activate it by holding both keys for that time 🤔. Windows 10 v1809