Inconsistent behavior with dead keys using Mod Tap

[rose hull]

I own a Wooting 60He+ and have noticed inconsistent behavior when using Mod Tap with dead keys.
For instance, I’ve assigned Mod Tap to the ESC key so that a long press sends ESC, while a tap sends ``~. This is necessary because, when using the "US International - Standard" layout, this key acts as a dead key used to type accented characters like è, à, ì, ò, ù`.

The issue is that when I try to type an accented character, for example, pressing " ` " followed by e , the result is sometimes e' instead of the expected é.
This seems to depend on the timing between the two key presses.

The problem is easy to reproduce: just set your layout to "US International - Standard" and assign the backtick key ( ` ~ ) to a Mod Tap key. Then try typing accented characters using that Mod Tap key.

Please fix. it's very frustrating to type quickly and get incorrect output.
The only workaround is to deliberately wait for the backtick key to fully release before pressing the next letter, which slows down typing considerably.

[tender zodiac]

Mod Tap’s Tap, actuates on release. There’s no way to get around that. Maybe you could try DKS (where you’d press shallowly for ~``` and deeper for Escape). Though to press Escape, ~``` will be pressed first, I’m not sure if that’d be a problem.

[rose hull]

If it only triggered on key release, the behavior would be consistent. However, as you can see from the graph, sometimes it works and sometimes it doesn't, even a slight difference in typing speed is enough to make it fail.

[tender rapids]

given that both still are backtick then E it could also be some OS event queueing

doesnt even make sense that the tighter time is the one it printed correctly

could you include spacebar for the graph and redo the test and send a similar screenshot with both cases next to each other?

[rose hull]

I don't think it's related to the operating system, as I tested it on Linux as well and observed the same behavior. You have to type extremely fast to avoid the issue, whereas with normal typing it almost always occurs.

I'm attaching a new graph, the larger spacing for the space key is due to several attempts before I managed to type fast enough.

Try it yourself maybe it's just an issue with the firmware version? I'm using the latest firmware version: v2.11.0-beta.1.

The firmware algorithm probably needs improvement when pressing silent keys with mod-tap.

[sterile eagle]

I just tried this and I'm unable to detect any unintended behaviour

everytime I hadn't fully released the backtick key before pressing e, I would get e` and anytime I properly pressed backtick first to toggle the deadkey behaviour and then e, I got è

it seems consistent for me