Closed ScottCE closed 2 years ago
/bugreport
Hi there!
We need a bit more information to really debug this issue. Can you add a "Report Bug" zip file here? You right click on our system tray icon and just go to report bug. Then drag the zipfile from your desktop onto the GitHub comment box in this issue. Thanks!
Should be attached to this comment. PowerToysReport_2022-05-09-08-53-58.zip
Thank you. After you disconnect and reconnect a monitor, the system can give it another name which is used as a key in FancyZones. So since FancyZones sees a new name, it treats the monitor as a new and applies a default layout there. It's a known problem, I'll close this issue as a duplicate. /dup of https://github.com/microsoft/PowerToys/issues/16370
Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
Microsoft PowerToys version
0.58.0
Running as admin
Area(s) with issue?
FancyZones
Steps to reproduce
I have not tested to see if this issue occurs without the use of a custom layout, but that is a circumstance of my issue. I have just started using FancyZones with version 0.57.2, but have been using PowerToys since v0.11.0 and this is the first issue I've had with any of the features that was obvious enough to report a bug.
EDIT: After reviewing a few of the previously-opened Issues, I realize that my KVM configuration may have something to do with this issue. Added new steps 3 and 4 to account for this possibly being the true issue, however testing the use of the KVM & DP switches after the upgrade to 0.58.0 does not cause the issue to reoccur.
✔️ Expected Behavior
Upgrading to 0.58.0 from any prior version would not modify the selected FancyZones layout selections.
❌ Actual Behavior
Upgrading to 0.58.0 from 0.57.2 modified or reset the FancyZones layout selection to "Columns" and/or "Priority Grid."
Other Software
N/A