-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
All my zones were resized. #19735
Comments
I have experienced something similar on my computer as well (without a power failure). Do you have the option enabled to treat all your screens as one screen (so you can make zones that span screens)? I have two 4k screens rotated to portrait mode and one laptop screen, all active. The laptop screen is to the bottom right of the two 4k screens. I have tried with all at 150% scaling. Usually I prefer the two 4k screens at 150% scaling and the laptop screen at 125% scaling. But I can't get FancyZones to be useful on my PC because of the tendency for zones to resize themselves. |
I don't think I've ever used that option. and I don't use any display scaling either. This issue doesn't happen frequently, but often enough that it's annoying with how many zones I have to resize. I'm just confused as to why the file is even being changed in the first place, if a user isn't explicitly saving a layout. I feel like not doing that would resolve the majority of the issues I've had with zones. |
Hi, can you please attach a /bugreport so I can see more details? |
Ref: #19423 |
Working on that file, but in the meantime I'll note that unlike that report:
|
Here's the bug report |
Thank you for the report. |
You mean after I fixed them? No it did not. However, my ref-width and ref-height have been set to the same (correct) values since before it was changed from zone-settings.json to custom-layouts.json (quite some time). |
Checked the saved |
Well, as I said previously, there are some big differences between what I experienced, and the details in that report. For one, that report says it only happens on their secondary monitor, and only when it's set to portrait, and while I do have a secondary monitor set to portrait, it only affected the zones on my primary monitor, which is not set to portrait. Still it seems like all these issues, and whatever other issues I encountered in the past that resulted in the custom-layouts/zone-settings file being deleted altogether, would be resolved if custom-layouts.json simply wasn't altered, manipulated, or otherwise messed around with unless a user is explicitly making changes and saving them from the editor. It seems odd that any routine exists whatsoever that--without any prompt to the user--changes every instance of "256" to "250" (among other changes) in that file. |
Those things aren't make difference for FZ, the key things are monitor id and work area size. /dup of #19423 |
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.60.0
Running as admin
Area(s) with issue?
FancyZones Editor
Steps to reproduce
I have no clue what happened. My computer shut down due to a power outage, and when I turned it back on, I opened powertoys to find that every single one of my 256x144 zones had been resized (and some slightly moved) to 250x144. I checked the json file as well, and sure enough, every single zone has been resized there. All I know for sure is that windows installed updates during the reboot. I'm unsure if I had installed a powertoys update at some point prior to that reboot, as my system had been on for a long time. Not the first time I've encountered a bug like this (where zone settings were changed (or sometimes erased entirely) when rebooting. Not sure why that file is being modified so much when the editor is not explicitly opened and the user isn't issuing save commands from there.
✔️ Expected Behavior
No response
❌ Actual Behavior
No response
Other Software
No response
The text was updated successfully, but these errors were encountered: