I know KM can’t “know the future” when tapping, but isn’t the simple solution a user defined delay on each tap, with the macro listening for another tap? That’s how Controllermate solves it (although it is an ordeal to setup tapping, compared to KM’s simple selection)
So it would go like this
Tap once, macro waits .1 seconds, no second tap, then initiate macro 1.
Tap once, macro waits .1 seconds, second tap, wait .1 seconds, no third tap, initiate macro 2.
And so forth.
I tried inserting delays at the head of the second macro but that didn’t work.
Short of this, we need better documentation of successful ways to defeat the errors that happen when the first tap launches macro 1 and then second tap launches macro 2.
I can’t find the pattern.
I struggle for hours trying to defeat it. Eventually I figure out the right combo so that the macros flow smoothly together, but sometimes identically solutions for seemingly identical UI fails. I even have a tap once for mouse click on one part of the GUI, and tap twice click on an identical function a few pixels away and it fails. Nothing else in the macro.
I’ve tried inserting timing changes everywhere.