Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FancyZones doesn't remember layout for one monitr/duplicates settings #19279

Closed
1 task done
Bubbsnbug opened this issue Jul 9, 2022 · 6 comments
Closed
1 task done
Labels
Issue-Bug Something isn't working Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@Bubbsnbug
Copy link

Microsoft PowerToys version

v0.60.0

Running as admin

  • Yes

Area(s) with issue?

FancyZones

Steps to reproduce

Have a 3 monitor setup. Launch FancyZones Editor and specify a different layout for Monitor 3. The layout assigned to Monitor 2 is always applied when closing.

✔️ Expected Behavior

The ability to apply an individual layout to each monitor. Works for Monitors 1 and 2, however Monitor 3 always reverts to match Monitor 2.

❌ Actual Behavior

The layout assigned to Monitor 2 is always applied to Monitor 3.

Other Software

No response

@Bubbsnbug Bubbsnbug added Issue-Bug Something isn't working Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams labels Jul 9, 2022
@misspent
Copy link

misspent commented Jul 9, 2022

I'm also having this issue as of the most recent public release

@mobelby7
Copy link

I have three monitors (two 4K and one HD).
This issue occurs with my two 4K monitors and is quite frustrating

@Bubbsnbug
Copy link
Author

I have three monitors (two 4K and one HD). This issue occurs with my two 4K monitors and is quite frustrating

Yes, I have the same setup. Should have clarified this, Thank you. HD monitor will maintain its own FancyZone layout, the two 4K monitors always mimic the layout assigned to Monitor2.

@SeraphimaZykova
Copy link
Collaborator

SeraphimaZykova commented Jul 11, 2022

Thank you for the report. We're preparing the fix. Can you please test the build with the fix mentioned here? #19203 (comment)

Please keep discussion on that new issue as well. Thank you!

/dup of #19203

@ghost
Copy link

ghost commented Jul 11, 2022

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!

@ghost ghost closed this as completed Jul 11, 2022
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams labels Jul 11, 2022
@ghost
Copy link

ghost commented Jul 11, 2022

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!

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug Something isn't working Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

4 participants