DisplayFusion RSS: Moving Window to Next Monitor not working since 9.6 (Beta 4)

RE: Moving Window to Next Monitor not working since 9.6 (Beta 4)

Binary Fortress Software — Mon, 16 Dec 2019 19:25:01 GMT

That's great news... thank you for your help.

RE: Moving Window to Next Monitor not working since 9.6 (Beta 4)

Binary Fortress Software — Mon, 16 Dec 2019 19:20:46 GMT

Thanks! We were finally able to reproduce it here as well and we'll have it all fixed up for good in Beta 8

RE: Moving Window to Next Monitor not working since 9.6 (Beta 4)

Binary Fortress Software — Mon, 16 Dec 2019 19:01:01 GMT

At 11:58 and around 40 seconds, i clicked the icon to move the window to the next screen. if you're not able to reproduce the issue, i could try a few more things for you.

RE: Moving Window to Next Monitor not working since 9.6 (Beta 4)

Binary Fortress Software — Mon, 16 Dec 2019 18:06:50 GMT

Thanks for the update, sorry to hear that it's still giving you trouble! Could you send us a debug log? Here are the steps:

On the DisplayFusion Settings > Troubleshooting tab, change the Logging drop-down to "L1: Log Minimal" and click Apply
Reproduce the issue and note the time so we'll know where to check in the log file
Click the "Export Info to File" button on the Settings > Troubleshooting tab
Reply with the file attached
Disable debug logging after sending the log

RE: Moving Window to Next Monitor not working since 9.6 (Beta 4)

Binary Fortress Software — Mon, 16 Dec 2019 17:04:42 GMT

soooo wierd... I just updated to Beta 6 and Ctrl-Win X (or clicking the icon at the top of each window) won't move the window to the next Monitor again. I'm able to use Shift-Win to move the window around. I don't know if it's related or not, but I can tell when this is going to break. I have a Trigger that puts the Display Fusion Settings window at a specific location when I open the settings window. That trigger doesn't work at the same time the Ctrl-Win X doesn't work. And on the same note, when the trigger puts the Settings windown in the correct place, then the Ctrl-Win X works properly.

RE: Moving Window to Next Monitor not working since 9.6 (Beta 4)

Binary Fortress Software — Wed, 11 Dec 2019 15:52:33 GMT

Strange! Glad to hear it's all good now. Definitely let us know if you run into this again.

Thanks!

RE: Moving Window to Next Monitor not working since 9.6 (Beta 4)

Binary Fortress Software — Tue, 10 Dec 2019 22:14:42 GMT

Last week I upgraded to beta 5 and it still didn't work. I rebooted, and still... didn't work. however, and I don't know why... but, today it's working. I'll obviously let you know if it stops working again. Thanks for your help

RE: Moving Window to Next Monitor not working since 9.6 (Beta 4)

Binary Fortress Software — Mon, 09 Dec 2019 16:37:35 GMT

If you haven't already updated to 9.6 Beta 5, could you give it a try? This issue should be all fixed up.

Thanks!

RE: Moving Window to Next Monitor not working since 9.6 (Beta 4)

Binary Fortress Software — Fri, 06 Dec 2019 20:56:41 GMT

I was using the Ctrl Win X and Ctrl Win W to move next and previous... I also tried to click the icon thats placed at the top of every window.

RE: Moving Window to Next Monitor not working since 9.6 (Beta 4)

Binary Fortress Software — Fri, 06 Dec 2019 18:44:51 GMT

Could you send me a copy of your troubleshooting info? Here are the steps:

Open the Settings > Troubleshooting tab
Click the "Export Info to File" button
Reply with the file attached

RE: Moving Window to Next Monitor not working since 9.6 (Beta 4)

Binary Fortress Software — Fri, 06 Dec 2019 14:14:02 GMT

You dont say which method you are using to move the active window but one way is the keyboard shortcut - press and hold the Winkey+Shift then tap the arrow keys either left or right.

Moving Window to Next Monitor not working since 9.6 (Beta 4)

Binary Fortress Software — Fri, 06 Dec 2019 12:33:56 GMT

Moving Window to next or previous monitor broke in 9.6 Beta 4. After updating to Beta 5, it worked for a bit. It stopped working again after I rebooted my computer. Has a setting changed that enables or disables this function?