Hi everyone,
I'm trying to migrate across from Logi Options+ and have run into a very specific issue. While I have managed to configure most things, I'm struggling with an app specific sequence. I have all four directional drags assigned to different actions on several buttons.
Previous setup with Options+:
Click+drag down sends F12 (from Options+)
BTT assigns F12 to two actions: keyboard key 's', then left mouse down event
'S' picks the scroll tool in my app and the mouse down event simulates holding the left button so I can move the mouse around and scroll through images without the strain of actually holding the button. I can't reproduce the same behaviour purely within BTT, either by using the same F12 workflow or directly assigning "s -> left mouse down" to the click+drag gesture as below
The problem arises because holding the left mouse button down for too long without any mouse movement creates strange blocking behaviour in my app, so the mouse down event needs to be swiftly followed by mouse movement. But the click+drag gesture seems to swallow the mouse movement, and even if I move the mouse instantly after triggering the gesture the blocking behaviour still occurs.
I've tried adding both blocking and non-blocking pauses before/after 's' in the sequence, which don't help. I've tried designating left mouse down as a named trigger, and putting the named trigger after 's' in the workflow. I can't assign the left mouse down event to the click+drag button release, because the drag cancels the button release recognition. No lengths of pauses make any difference, and nor does clicking the advanced setting "allow mouse movement while button is pressed".
If anyone can understand what I'm trying to achieve, are there any suggestions for how to get around this? I want it to all be contained within one button gesture rather than just assigning another button to fire the left mouse down event, as I have other shortcuts on the other buttons.
Thanks in advance!
