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: When a window in a zone is closed and reopened, FZ seems to get confused #17387

Open
1 task
SCWells72 opened this issue Mar 31, 2022 · 2 comments
Open
1 task
Labels
Issue-Bug Something isn't working Needs-Team-Response An issue author responded so the team needs to follow up Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams Product-FancyZones Refers to the FancyZones PowerToy

Comments

@SCWells72
Copy link

Microsoft PowerToys version

"0.57.0"

Running as admin

  • Yes

Area(s) with issue?

FancyZones

Steps to reproduce

  1. Start an app and arrange its window into a zone that's not the first on that screen.
  2. Stop the app and restart it.
  3. The window will either be placed into the original zone properly or will be just slightly offset from that zone.
  4. If it was placed into that zone properly and you use the keyboard shortcut for next zone while that window has focus, it will move to the first zone on that screen instead of realizing that it's already where it should be and moving to the next zone.
  5. If it slightly offset from the original zone, you must of course place it back into that zone. I do that using the keyboard shortcut for previous or next zone respectively depending on whether it's offset to the left or right of the desired zone.

✔️ Expected Behavior

It seems like these windows should be restored into the same zone according to the "Move newly created windows to their last known zone" setting which I have enabled. And like I said, sometimes that kind of works in that it will start in that zone but seemingly without the proper zone number assigned for purposes of the move-to-next/previous-zone action. Other times it seems to just miss being moved into the right zone. It just doesn't seem like that setting works properly.

❌ Actual Behavior

Described in the steps to reproduce section.

Other Software

No response

@SCWells72 SCWells72 added Issue-Bug Something isn't working Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams labels Mar 31, 2022
@franky920920 franky920920 added the Product-FancyZones Refers to the FancyZones PowerToy label Mar 31, 2022
@SeraphimaZykova
Copy link
Collaborator

Does it happen with the latest version of PowerToys?
/needinfo

@ghost ghost added Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something and removed Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams labels May 10, 2022
@SCWells72
Copy link
Author

Hi, @SeraphimaZykova. Thanks for following up. It's significantly improved in the latest version with windows restoring properly in the original zone, even with squared corners on Windows 11 if so configured. So that's great!

I was thinking about filing a new bug/enhancement request on this exact feature, though, for when the same application creates multiple windows so that perhaps it uses a composite key based on both the process name and the window title. For example, I use an IDE (IntelliJ IDEA) to develop a plugin for the same IDE which is launched via the interactive debugger. The main IDE dev instance is in a zone on my left monitor while the debug instance that it launches should appear in a zone on the right monitor so that I can debug it conveniently. However, presumably because these are the same core process, the debug instance often shows up in the same zone as the dev instance and I have to immediately move it.

Should I file a separate issue here for that, or does one perhaps already exist?

@ghost ghost added Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams Needs-Team-Response An issue author responded so the team needs to follow up and removed Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels May 10, 2022
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-Team-Response An issue author responded so the team needs to follow up Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams Product-FancyZones Refers to the FancyZones PowerToy
Projects
None yet
Development

No branches or pull requests

3 participants