MX Master drag action sequence

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!

are you releasing that left mouse down click somewhere again? Otherwise this can lead to very weird behavior because that click will be kind of stuck.

Possibly instead of using the custom click you could use the predefined action "Start Mouse Drag", but that would also need to be canceled ad some point by a "Stop Mouse Drag"

Thanks Andreas, I have given it a try but unfortunately that doesn’t work. I’ve tried a bit more troubleshooting and realised that if I just assign the sequence or F12 workflow to the button via the ‘action executed on click release’, it works, but it triggers the odd behaviour in app if it’s assigned either to the action on button press or the button drag. I presume this is something to do with how either BTT or the target app interpret whether a physical button is still being held down or not, and what signal BTT sends as a result? The action executed on click release isn’t recognised after a drag gesture, so I don’t think I can daisy chain the drag (for the tool select) AND click release (for the left mouse down) if the latter won’t fire, and I wouldn’t want the left mouse down happening after the other directional drags.

Anyway, I think for my sanity I will try dedicating a separate button to this workflow using the click release trigger and seeing if I can just adapt to a swap in button functions.

Thanks for your quick response, as always

I think I might not have fully understood the use case. Maybe a quick video could help, or if you could tell the exact app you are trying this with, then I could try to set it up myself.

Sorry, I realised as I was trying to describe it all that it sounds very confusing! The app is Osirix MD which is a DICOM viewer for radiology, and requires a paid subscription for use. Don't worry for now - I've got it set to another button and it seems to work well like that. If I have further problems I'll create a video and try to provide a more understandable explanation. Thank you for your responses