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 restores child window position to main window position #30071

Open
W4RH4WK opened this issue Nov 29, 2023 · 3 comments
Open

FancyZones restores child window position to main window position #30071

W4RH4WK opened this issue Nov 29, 2023 · 3 comments
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

@W4RH4WK
Copy link

W4RH4WK commented Nov 29, 2023

Microsoft PowerToys version

0.75.1

Installation method

Microsoft Store

Running as admin

No

Area(s) with issue?

FancyZones

Steps to reproduce

  • Tick "Move newly created windows to their last known zone"
  • Untick "Allow child windows snapping"
  • Start Visual Studio 2022
  • Snap main Visual Studio window to a zone
  • Drag a tool window outside the main Visual Studio window
  • Close Visual Studio
  • Start Visual Studio

The detached tool window is placed over the main window by fancy zones

✔️ Expected Behavior

With "Allow child windows snapping" off, FancyZones should not reposition child windows.

With "Allow child windows snapping" on, FancyZones should remember child window positions and correctly restore them on program launch.

❌ Actual Behavior

The child window position is always restored to the main window position, effectively covering the whole main window on program launch.

Other Software

Visual Studio 2022
(probably all Apps featuring child windows)

@W4RH4WK W4RH4WK added Issue-Bug Something isn't working Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams labels Nov 29, 2023
@davidegiacometti davidegiacometti added the Product-FancyZones Refers to the FancyZones PowerToy label Dec 2, 2023
@SeraphimaZykova
Copy link
Collaborator

Could you please check if it's still reproducible on the 0.76 version? /needinfo

@microsoft-github-policy-service microsoft-github-policy-service bot 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 Dec 5, 2023
@W4RH4WK
Copy link
Author

W4RH4WK commented Dec 5, 2023

Yes, still reproducible with 0.76.

@microsoft-github-policy-service microsoft-github-policy-service bot 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 Dec 5, 2023
@SeraphimaZykova
Copy link
Collaborator

Thank you for checking. I was able to reproduce the problem; it happens only after opening, but when you try to drag the Solution Explorer window, the zones won't be triggered if the Allow child windows is not enabled.
It turned out that the Solution Explorer window appears when the main window is not yet visible, so it's not considered a child window. We'll figure out what we can do to resolve this problem. Thanks.

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