Bug?? Minimum time key down

@Andreas_Hegenberg If I want to trigger two actions with one shortcut (key down), one immediately and one after a second, I would set it up like this:
0 s
1 s
But that doesn't work. The minimum hold time must be 0.05 s.

That's inconvenient for me. I would like the first action to be triggered immediately. Is this a bug?

Edit: I could set the first action to 0 s (key down). And the second action to trigger after 1 s at key up.

But it's more convenient to trigger the second action at key down as well. That way, you can see how the action is triggered and only then release the key.

That is true, this limitation was necessary until a few versions ago, but I recently improved something in the long press handling and now it shouldn't be required anymore. I'll remove that limitation with one of the next alphas.

Very nice, thank you!

Interestingly, this minimum is only 0.01 s when the second action is triggered by key up. But that is “psychologically” inconvenient.

May I ask another question on the same topic? What is the opposite of this?

It's about the fields. How do I define all fields that do not contain “Text” or “Web” in their name? I'm somehow too stupid to do this myself. :upside_down_face:

You can change "Any" to "None" in the dropdown above "focused element role".

5.671 should allow mixing 0 minimum down with long press. However I need to do some thorough testing as I might not see the full impact of this change yet.

Good morning, Andreas.

Thank you very much :slightly_smiling_face: . I have started testing 5.671. As far as I can see, everything is working as expected.

So far, I have only found one setup where “0” does not work. BTT then displays a conflict menu.

But that has always been the case. The difference to the last version is that now 0.01 is sufficient, which is perfect (for me).

So, this is how you avoid the conflict menu, If both actions are set up to trigger on key down.

*********************************************************************************

I'll let you know if I discover anything else.

coukd you copy & paste these two triggers that cause the conflict menu here? Probably I missed some case

I have already adjusted everything. But the “error” is easy to reproduce.

I have set up two new triggers with “s.” The conflict arises when the first action is set to 0 s. The solution is to use 0.01 s.

s 1 Aktion.bttpreset (1.2 KB)

s 2. Aktion.bttpreset (2.3 KB)

Edit: Ah, and thank you for your help with the conditions :slightly_smiling_face:

One more thing: When BTT recognizes the conditions as true in a CAG, the font turns green. Is that the exact moment when a trigger should work? Or is it normal that it takes some time after recognition?

I'm asking because BTT takes more time for me.

weird on my tahoe machine these triggers work fine on 5.671 (first types s, then shows the HUD). I'll check with another machine tomorrow

I use Ventura, not Tahoe. Do you think that matters?

After testing it for a while, I can say that the second action (Hud) always works, always! But the first one is quite buggy (the letter 0.01 s).

The letter suddenly stops being typed. I'm still trying to figure out when this happens. To get it working again, BTT has to be restarted. Sometimes it's enough to change the front app.

It would be great if you could find the bug :slight_smile:

Could you check whether 5.673 helps? (especially when configured with 0 delay)

Unfortunately, nothing has changed. BTT still shows a conflict menu with 0.

Weird. Could you try to import the two bttpreset files you posted? (Maybe something is set on import that makes it work)
Might need to clear the BTT trash first

Okay, I'll do that right away.

Just so you're fully informed, these triggers are in a CAG with these conditions. In case that could be relevant.

Ah, that might be relevant! I'll check

//edit: yes! I can reproduce the issue while in a CAG. I'll look into it.

And there is a second CAG with the opposite conditions and the same triggers.

Great!!!

5.674 now applies the same changes to the CAG code.

1 Like