I've been trying to get this to work with some of the programmable buttons on my Logitech G604 Mouse, but with no luck so far.
Just to make sure I understand, I should be able to set up a macro that's triggered when a programmable button is pressed only once, then a different macro that's triggered when the same button is pressed only twice, etc.?
Or am I misunderstanding this new trigger functionality?
I'll be honest: that slipped by me at release! Brilliant that KM has proper multi-press functionality now!
Yes, it's basically the same, except that my templates are tweakable, and therefore slightly more responsive, as far as I can tell. You also only have to set two triggers to get access to single, multiple or short/long presses all at once.
@peternlewis is the ~1sec lag with multiple taps due to allowances for slower tappers? If so, is there a global preference for that to make it a bit snappier?
I support that. Setting the time individually seems important to me. And what I have never understood: Why is long press not triggered when the key is down? Wouldn't that be more intuitive? If I'm not mistaken, this is the case in @noisneil's macro. You should also be able to set this time. So, if the key is hold longer than x seconds.
You make me curious, but you don't tell me anything.
But I can tell you how I imagine it as a beginner.
⌘+1. After the "1" is up, KM waits a certain amount of time (adjustable) until the action is executed.
⌘+1+1. Is triggered when the time between "1" and "1" is undershot.
⌘+1 long press. Is triggered if "1" remains pressed for a minimum time. Trigger on key down, so that you can see how the action is executed.
They are controlled by the double click interval. They can be down for at most the double click interval and up for at most twice that. For an "only" to fire, they must be up for at leas twice the double click interval before the trigger can fire.
You can override the times with the MaxTapDownTime and MaxTapUpTime preferences as documented.
I did, but I just tried again and this time it worked! Much better at 0.2s, I think.
I have to agree with @Frankb that long press should trigger once the time threshold has elapsed rather than upon release. Far more intuitive.
As things stand, I think the only real advantages of my template are that you can add unlimited tap numbers (not that I can imagine wanting more than three), the long press behaviour is arguably better and the tap speed can be defined by the user.
I've added an updated and improved version at the top here:
Thanks, Peter. Is there any reason why this wouldn't be working when trying with my Logitech G604 Mouse?
For example, I created Macro A to launch App A when Button X "is tapped only once." And then I created Macro B to launch App B when Button X "is tapped only twice." Neither macro is working. (However, either macro works just fine when the trigger is set back to "is pressed.")
In the meantime, I'll state the obvious by saying that the reason I prefer the other behaviour is that you can hold the key for as long as you like and be sure it will trigger, which also reduces the chance that you'll release it too early.