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 layout syncing #10603

Closed
brendanefro opened this issue Apr 5, 2021 · 6 comments
Closed

Fancyzones layout syncing #10603

brendanefro opened this issue Apr 5, 2021 · 6 comments
Labels
Idea-Enhancement New feature or request on an existing product Product-FancyZones Refers to the FancyZones PowerToy Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@brendanefro
Copy link

📝 Provide a description of the new feature

What is the expected behavior of the proposed feature? What is the scenario this would be used?

I have multiple computers with which I use Fancy Zones, It would be great to sync layout settings among them.

If you'd like to see this feature implemented, add a 👍 reaction to this post.

@brendanefro brendanefro added the Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams label Apr 5, 2021
@SeraphimaZykova SeraphimaZykova added Idea-Enhancement New feature or request on an existing product Product-FancyZones Refers to the FancyZones PowerToy labels Jul 22, 2021
@craigloewen-msft craigloewen-msft removed the Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams label Oct 1, 2021
@dedavis6797
Copy link
Contributor

dedavis6797 commented Oct 1, 2021

Good feedback, we've received similar requests for all PowerToys settings to be synced between devices. @SeraphimaZ in the meantime while we plan out this functionality, could a user export their settings.json file to other devices and get the same layout configurations? Or is this a more involved process?

@SeraphimaZykova
Copy link
Collaborator

The settings.json with FancyZones settings could be copied as it is.
Regarding layout settings, it's more complicated. We need to figure out how to bind layouts with the new configuration and probably include some additional data in the zones-settings.json. Currently, each layout is bind with the monitor id, monitor resolution, and virtual desktop id. Those parameters would be different on the other configuration.

@franky920920
Copy link
Contributor

Related: #3381

@cschonewill
Copy link

The settings.json with FancyZones settings could be copied as it is. Regarding layout settings, it's more complicated. We need to figure out how to bind layouts with the new configuration and probably include some additional data in the zones-settings.json. Currently, each layout is bind with the monitor id, monitor resolution, and virtual desktop id. Those parameters would be different on the other configuration.

One idea is that rather than tangling with the issue described around persistency is just allowing custom layout options to be exportable/importable elsewhere. Users could then select and setup from there. That's the rework that most of us who have suggested this would like to get around when we build custom workflows. The data of which screens and virtual desktops is a mess to deal with, but layouts that have been carefully made should hopefully be more portable and a user would simple re-assign them based on their other setup. For that, since resolutions and aspect ratios can differ as well, having layouts be percentage based rather than pixel based (or setting a toggle for this behiavor more likely) would help with the transportability. This would get most of us what we want I believe while also (I presume) being far easier to implement.

@cinnamon-msft
Copy link
Collaborator

/dup #3381

Copy link
Contributor

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-github-policy-service microsoft-github-policy-service bot added the Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. label Jan 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Idea-Enhancement New feature or request on an existing product Product-FancyZones Refers to the FancyZones PowerToy Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
Status: Done
Development

No branches or pull requests

7 participants