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

Changes from Zone Editor do not effect additional virtual desktops #36935

Closed
rausb opened this issue Jan 17, 2025 · 1 comment
Closed

Changes from Zone Editor do not effect additional virtual desktops #36935

rausb opened this issue Jan 17, 2025 · 1 comment
Labels
Issue-Bug Something isn't working Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams

Comments

@rausb
Copy link

rausb commented Jan 17, 2025

Microsoft PowerToys version

v0.87.1

Installation method

Microsoft Store

Running as admin

Yes

Area(s) with issue?

FancyZones, FancyZones Editor

Steps to reproduce

  • create at least one other virtual desktop
  • make changes to custom layout in the layout editor (in my case I deactivated zone gaps) and confirm
  • zone gaps disappeared from first desktop
  • switch to second virtual desktop
  • zone gaps will still be there

✔️ Expected Behavior

Zone gaps and other changes will effect all virtual desktops immediately after the change

❌ Actual Behavior

Zone gaps and other changes will effect the current desktop, only

Other Software

No response

@rausb rausb added Issue-Bug Something isn't working Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams labels Jan 17, 2025
Copy link

We've found some similar issues:

If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.

Note: You can give me feedback by 👍 or 👎 this comment.

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 Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams
Projects
None yet
Development

No branches or pull requests

1 participant