A few, probably related issues I ran into when using this function and also with a custom script trying to get around it that uses the 'BFS.Input.SetMousePosition(x, y)' function (yes, the x,y coordinates passed to it were calculated correctly).
All examples are with 2 monitors:
Primary = 1920x1200
Secondary = 1280x1024
And DisplayFusion v9.7.1
Expected behavior: when pressing the hotkey for the function the mouse will move to the same relative position (e.g. center to center) in the next monitor.
Actual behavior:
Row, primary on left, top edge of both at y=0: When used while the cursor is in the lower part of the lower resolution secondary monitor, the cursor moves to (primaryMonitorWidth, Y) of the primary monitor, as in right edge of monitor but with the correct Y value.
Row, primary on right, top edge of both at y=0: When used while the cursor is in the lower part of the lower resolution secondary monitor, the cursor moves to (primaryMonitorX, Y) of the primary monitor, as in left edge of monitor but with the correct Y value.
Diagonal, primary on bottom right, secondary top left (only corner is touching): Wherever used on either monitor, the cursor goes to (0, Y), the center edge (y value seems correct)
Diagonal, primary on top left, secondary bottom right (only corner is touching): Wherever used on either monitor, the cursor goes to (primaryMonitorWidth, Y), the center edge (y value seems correct)
Update: found a workaround, with custom function script bound to hotkey (though this obviously won't change mouse behaviour when dragging between monitors).
Script is published here.
This issue should be fixed up in the latest beta, available here: https://www.displayfusion.com/Download/Beta. Please let me know if you still run into any trouble after updating.
