Very recently, for whatever reason, whenever I use my middle mouse button to swap what monitor a window is on, it takes 5-10 seconds before the window will switch. Clicking the icon and using ctrl+win+x work fine and will swap the window immediately. But for whatever reason, using the middle mouse button there's a bit of lag. If I click multiple times, after the 5-10 seconds the window will swap monitors that many times. So if I click 4 times, after 5-10 seconds the window will swap, swap, swap, swap quickly.

Side note: the middle mouse button works for everything else for other programs and windows with no problems. It's only DisplayFusion

I have the exact same problem, which is very annoying since it's one of the features i use the most

This is happening to me, also. It's a good 1-2 second delay.

The same started happening to me today and I'm using beta4 since its release.

Once it's started, it was happening with all windows, regardless of application, display, moving direction and windowed/maximized state.
DF restart didn't help, PC restart fixed it temporarily.

Hi,

I can't reproduce the issue because I have no clue what brings it on. Today it started happening out of the blue after ~6hrs of uptime seemingly without any reason, I wasn't doing anything out of the ordinary. Again it could only be fixed with a PC restart and after that I've tried to redo everything I've been doing for the preceding hour but couldn't make the problem appear.
Also I can't enable logging, GUI says Error: Result is invalid. [System.Exception]
(although in the exported zip, there are two .log files which have content but the html just contains the same error, I'll leave it on if the textual debug log is enough)

I can't reproduce this consistently either. It's intermittent. Since creating this thread, the problem went away after an hour. Since then I've only experienced it once for maybe a few hours. I didn't turn any programs off, restart my machine, change any settings in DF.

I can reproduce this with an ahk script which sends a key down event only when a specific window is active.
- The issue stops happening only when a key up event for the same key is received in any window.
- Not a bug with the application: the issue persists even if the application quits.
- Not a bug with ahk: the issue persists when the script is restarted or even ahk is completely closed.
- Not key specific: reproducible bound to any hotkey, for any key that the key down event is being sent for (including special keys like Tab and Capslock).
- Not application specific: reproducible with any application.

I'm not sure this is the only thing that triggers this problem, this is just the one I could isolate and reliably reproduce it with.

Hope this helps. I can try to make a log if it's still needed.

Hi,

The .html still shows the error message only but the actual log is in there.
I did the repro with binding Capslock to Tab down event if notepad.exe is active (just for reference, behaves the same with any other application and key).
I'm using 9.7.2b4.

Hope this helps!

Hello,

Beta5 seems to have fixed this, at least for the use case I reproduced it with.

Thanks!