Scroll Up/Down triggers are not working as expected anymore since last few versions.
"BTTLastUpdatedAt" : 1696101027.432544,
"BTTTriggerType" : 119,
"BTTTriggerTypeDescription" : "Scroll Up (modifier key needed)",
"BTTIsPureAction" : true,
"BTTTriggerClass" : "BTTTriggerTypeTouchpadAll",
"BTTLayoutIndependentActionChar" : "UP",
"BTTAutoAdaptActionToKeyboardLayout" : true,
"BTTGenericActionConfig" : "autoAdapt",
"BTTShortcutToSend" : "55,126",
"BTTUUID" : "E9A1CE59-7E5B-42FE-96C8-470140510979",
"BTTEnabled" : 1,
"BTTEnabled2" : 1,
"BTTRequiredModifierKeys" : 1048576,
"BTTOrder" : 2,
"BTTGestureNotes" : "Scroll to Top"
If I manually press CMD+ ↑ it works ok. Any ideas why?
Seems to trigger fine here. Is the scroll direction still the same on your machine?
Yes. And this appears only sometimes, that's the problem. Sometimes it works, sometimes it doesn't. I feel like something might be out of or in focus. I am not sure yet.
Could you enable the "Show HUD when gesture is triggered" to see whether BTT recognizes the scroll correctly?
@Andreas_Hegenberg - Reproduced it right now on theverge.com. The HUD triggered and the scroll didn't work, it kinda choked for a few milliseconds and just did a regular scroll! Logs here.
weird, maybe something is stealing the keyboard focus. However then it also should not work when pressing the shortcut manually
Is it easy to reproduce on your machine or does it require many attempts?
I just reproduced it on theverge.com once again so I think it's easily reproducible, yes.
I can reproduce it, but can't see a reason why. It could be some change in how Safari handles simultaneous scroll & keyboard events.
However a simple workaround is to assign the predefined actions "Home (Beginning Of Page)" and "End (End of Page)" instead, Safari seems to handle these correctly always.
Nice, Safari works this way. Should the other apps work too?
Depends, the cmd+arrow shortcut has different functionality across apps, which might not always be the same as the home/end keys.
Sublime and Safari work. Looks good.
Nah, same issue on Sublime Text with this workaround, also...