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

Fancy Zones Resolution Change Taskbar overlap #4869

Closed
jsormaz opened this issue Jul 8, 2020 · 4 comments
Closed

Fancy Zones Resolution Change Taskbar overlap #4869

jsormaz opened this issue Jul 8, 2020 · 4 comments
Labels
Product-FancyZones Refers to the FancyZones PowerToy Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@jsormaz
Copy link

jsormaz commented Jul 8, 2020

Environment

Windows build number: Microsoft Windows [Version 10.0.18363.900]
PowerToys version: v0.19.1
PowerToy module for which you are reporting the bug (if applicable): Fancy Zones

Steps to reproduce

My monitor supports "Picture by Picture" which allows me to quickly change from full screen to a split screen layout (so I can have my work computer on half of my screen for example. However, whenever I enable/disable PBP, the fancy zones layouts break and now overlap the windows task bar (which I have set on the right hand side of my screen.

  1. Create zones layout
  2. Change monitor resolution
  3. Change monitor resolution back to original
    4, Original layout now overlap the taskbar

Expected behavior

Zones layout should not overlap taskbar after changing resolution

Actual behavior

Zone layout overlaps taskbar

@ghost ghost added the Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams label Jul 8, 2020
@Uiasdnmb
Copy link

Uiasdnmb commented Jul 8, 2020

Came here for exact same issue (also have monitor with PBP). I'll also add that this can be "fixed" by going into zones editor and hitting apply without doing any changes or restarting PowerToys alltogether.

Right now I've rolled back to v0.18.2 which is not affected by this issue.

@jsormaz
Copy link
Author

jsormaz commented Jul 8, 2020

Came here for exact same issue (also have monitor with PBP). I'll also add that this can be "fixed" by going into zones editor and hitting apply without doing any changes or restarting PowerToys alltogether.

Right now I've rolled back to v0.18.2 which is not affected by this issue.

Thanks for the tip! This is a decent workaround for now. Win+` brings up zones editor, hit apply.
I'll keep doing this until they fix it or I get annoyed enough to roll back to the previous release like you did.

@jsormaz
Copy link
Author

jsormaz commented Jul 8, 2020

Came here for exact same issue (also have monitor with PBP). I'll also add that this can be "fixed" by going into zones editor and hitting apply without doing any changes or restarting PowerToys alltogether.

Right now I've rolled back to v0.18.2 which is not affected by this issue.

BTW - completely unrelated, but it sounds like you have a similar setup to me. I highly recommend checking out the software called "Across Center". It lets you use your mouse/keyboard that is connected to 1 computer as a bluetooth m+k on another computer. seemless transition between the two just by dragging the mouse like you would with multiple monitors. This has made my WFH situation much more enjoyable.

@enricogior
Copy link
Contributor

@jsormaz @Uiasdnmb
same root cause as #4694
Closing this as duplicate.
Thanks.

@enricogior enricogior added Product-FancyZones Refers to the FancyZones PowerToy Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams labels Jul 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Product-FancyZones Refers to the FancyZones PowerToy Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

3 participants