I was able to reproduce that here so I've added it to our list to look into.
Thanks!
![User Image](https://secure.gravatar.com/avatar/48b3a65f192d65eaf822499ec85b78c6/?s=48&d=https://images.binaryfortress.com/General/UnknownUser1024.png)
Linfeng Li948660
22 discussion posts
Good to know! Will upgrade to v11.0.3, and keep log on. Thank you!
![User Image](https://secure.gravatar.com/avatar/48b3a65f192d65eaf822499ec85b78c6/?s=48&d=https://images.binaryfortress.com/General/UnknownUser1024.png)
Linfeng Li948660
22 discussion posts
I’d like to report that the flashing bug has been resolved in Version 11.0.5. However, I’ve noticed that the "Move Window to Previous/Next Monitor and Size Proportionally" function is now behaving differently. Specifically, when the resolution or layout of the target monitor differs from the source monitor, the resizing process takes noticeably longer and exhibits significant visual glitches. This issue might be related to my dual-GPU setup, which involves a total of seven monitors.
For now, using the simpler "Move Window to Previous/Next Monitor" function works well. It moves the window to the target monitor instantly without any delays or glitches.
<hr>
For demonstration purposes, I’m attaching a screen-recording showing the results of moving the DisplayFusion Settings window across all monitors. The test includes three scenarios: first using the plain "Move Window to Previous/Next Monitor" function, then using the "Move Window to Previous/Next Monitor and Size Proportionally" function, and finally switching back to the plain function. All function calls were triggered by the same hotkey, which I reassigned between test batches.
Starting at 00:38, one can observe visual glitches during the proportional resizing process. The Settings window repeatedly resizes back and forth when moved to monitor 2. At 01:22, after switching back to the plain function, the window moves seamlessly between monitors without the additional resizing overhead.
• Attachment [protected]: Clip_of_window_movement.mkv [11,040,290 bytes]
I was able to reproduce that here so I've added it to our list.
Thanks!