-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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]: workspace/virtual desktop <-> layout mapping #11125
Comments
Maybe Windows vNext related, since rolling back to 0.33.1 or 0.35.0 do not solved the issue. Also, removing temp data under Update: not reproducible on Windows stable. Maybe some special label is required? |
when you say workspaces, you mean virtual desktops? |
Yes.
|
This is also an issue for me. Other closed issues in this repo suggest that the layout per virtual desktop should persist, but changing layout on one desktop currently is breaking all my others. |
From my understanding and investigation (with me being completely uncomfortable and ignorant with cpp) the issue is with the registry key not being open when
Also experimenting with Problem is that is not very clear to me how to handle this kind of change, for example I can see the usage of The fix seems trivial: open before query. But looks like there is some magic to have the key always open (and thus this code is failing)? |
The missing regkey is Maybe a fallback to the canonical |
This is a valid scenario we need to address. @zadjii-msft anything else we need? @SeraphimaZ as fyi |
…back CurrentVirtualDesktop
In the meantime I updated my local branch to use a different approach with reg key open/read (I think more RAII compliant???) by using Let me know if you want me to refine this branch and open or document a bit more. Maybe this is a regression from
|
* fix(microsoft#11125): fallback to canonical regkey session unaware * chore(microsoft#11125): use wil::unique_hkey instead of HKEY for fallback CurrentVirtualDesktop * refactor: extract new explorer current virtual desktop behavior into a separate method
Resolved. |
Microsoft PowerToys version
0.37
Running as admin
Area(s) with issue?
FancyZones
Steps to reproduce
✔️ Expected Behavior
Fancy zones for each workspace are persisted and correctly mapped.
❌ Actual Behavior
Every Fancy zone layout change is applied to every workspace.
Other Software
The text was updated successfully, but these errors were encountered: