Since the latest update (6.286) a few of my custom shortcuts are no longer working as expected.
I have two simple shortcuts for mouse buttons 3 and 4 (back and forward), so that combined with pressing Cmd, it will send Cmd + Alt + arrow left/right. The goal is to move between tabs in my browser, instead of going back/forward in that tab's history.
Before the update I could simply hold Cmd and press either of the mouse buttons whenever I wanted, and it would respond as expected. After the update, I can only hold Cmd for a single direction, and I have to release and re-press it before I can continue cycling the tabs the other way. Otherwise it does revert back to the default behaviour of moving through the tab's history. This goes against years of muscle memory. Can BTT quit willy-nilly breaking things that people have trained themselves on for years? Especially since it's a program that positions itself as the tool for (re)gaining control over gestures/shortcuts/etc.
A few important points about my triggers:
I originally had it set to only trigger keydown events, as that is also when the browser responds to tab navigation. Responding to keyup is too late and will actually cause it to BOTH go back/forward in history AND move a tab to the left/right. Due to the latest update I was forced to change it to keydown + keyup, otherwise the command key would remain stuck.
The triggers can be repeated by holding the buttons, which forces BTT to “Trigger on Mouse Down”.
I also noticed that moving the mouse however slightly between button presses does allow it to trigger the shortcut every time. But this is even more unnatural than just releasing and re-pressing Cmd. To be sure, I tried with Allow mouse movement while button is pressed both disabled and enabled, and it doesn't seem to make a difference for pressing Cmd + mouse button without moving the mouse cursor.
For point 1. if I understand correctly you seem to confuse trigger/action. Your action was set to only press the key down - which is almost always wrong as that will always lead to a pressed keyboard key. Your mouse trigger can still trigger on key-down (which is also the default)
Could you maybe copy & paste the setup for the mouse buttons here? (Select them in BTT, copy, then paste the JSON here - if possible put it in three backticks or use the "preformatted text" option here:
It looks like Include modifier keys already worked on the older version, and the latest version doesn't seem to need it at all anymore. I also noticed that prior to the latest update, it would sometimes miss the trigger and still go page back/forward instead of moving between tabs. This was also solved either by enabling Include modifier keys or updating to the latest version.
Is there any downside to just always enabling the setting?
yes, the setting only works if the shortcut you are sending already contains all of your currently pressed modifier keys. If you hold cmd and your shortcut is cmd+opt+arrow left, that will work fine. If you hold ctrl and your shortcut is cmd+opt+arrow left it would not work because then it would send ctrl+opt+arrow left instead.
However with the latest build this should not be necessary anymore for your usecase.
Alright, based on that description it does sound like I would need to keep it disabled, to prevent any weird interactions. I'll check for a few days to see if the shortcuts remain stable, but from my quick testing it does seem to be solved, so thanks.
