Under VERY particular circumstances (I'm not exactly sure what they are but I have a method of reproducing somewhat reliably), the function to move a window fails to do so correctly. Once it has failed to do so, all subsequent requests to move the same window fail as well, including those from "higher level" functions like "MoveToRightMonitorHalf".

My current setup is 3x 2560x1440 displays set in a 3x1 surround configuration with 120px bezel correction between each display. I have nvidia's smartmaxapp disabled, and I have windows taskbar disabled. DF's multi-monitor taskbar is enabled, and I have the normal windows taskbar on the center display. All DF taskbars and the Windows taskbar are set to auto-hide and are half-height (small taskbar). I have window snapping enabled in DF as well.

My method to reproduce the issue is as follows:

• Create a small window in the center display (notepad works fine)
• drag the window to the bottom right corner of the display, such that both the right and bottom edges of the window are out of the center display's bounds
• Drag the window up until it snaps to the bottom edge of the display
• Drag the window to the left until it snaps to the right edge of the center display without unsnapping from the bottom in the motion
• at this point, the window should be snapped to the bottom right corner of the center display. I've confirmed with multiple tools that its positioning is EXACTLY the same as instances where the function did not fail and it was also snapped in this position, but I think typically those were snapped from inside the display going out, rather than from outside the display going in.
• use a keyboard shortcut to trigger a function to move the window
• Rather than moving, the window will occasionally stay in place, but other functions (such as size) will still run on the window

In case it wasn't clear before, it's not that the function itself occasionally works or doesn't work. Rather, the window itself is occasionally put in some sort of state which causes the functions to ALWAYS fail. If the window enters this state, only moving the window (even a small amount) frees it and allows functions to move it again. Otherwise, functions will work just fine 100% of the time. At the moment the window is snapped in the position mentioned above, it is already determined from that point on whether or not the fuction will fail.

I'm on beta 10 at the moment.

Awesome, thanks!

I have yet to be able to reproduce the bug on Beta 11. All seems good for now, thanks!