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.

Sign up for GitHub

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

Jump to bottom

Move newly created windows to their last known zone - does not work for certain processes #369

Closed
wilhelmmedetz opened this issue Sep 13, 2019 · 2 comments
Closed

Move newly created windows to their last known zone - does not work for certain processes #369

wilhelmmedetz opened this issue Sep 13, 2019 · 2 comments
Labels
Issue-Bug Something isn't working Product-FancyZones Refers to the FancyZones PowerToy Resolution-Fix Committed Fix is checked in, but it might be 3-4 weeks until a release.
Milestone
0.14

Comments

@wilhelmmedetz
Copy link

Environment

Windows build number: 10.0.18362.356
PowerToys version: 0.11.0
PowerToy module for which you are reporting the bug (if applicable): FancyZones

Steps to reproduce

  1. Configure 'Move newly created windows to their last known zone' ton On.
  2. Open an window
  3. Move it into a zone
  4. Close the window.
  5. Reopen the window.

Expected behavior

Reopened window should be at the exactly same position where it was closed.

Actual behavior

Affected applications: Explorer, Notepad2, Google Chrome

Sometimes the reopened window is at a completely different position on the screen.

Sometimes the reopened window is almost at the correct position, but a few pixels off.
@enricogior enricogior added Issue-Bug Something isn't working Product-FancyZones Refers to the FancyZones PowerToy labels Sep 13, 2019
@enricogior
Copy link
Contributor

@bzoz you may have already fixed this one.

@enricogior enricogior added the Resolution-Fix Committed Fix is checked in, but it might be 3-4 weeks until a release. label Nov 22, 2019
@enricogior enricogior added this to the 0.14 milestone Nov 22, 2019
@crutkas
Copy link
Member

crutkas commented Dec 2, 2019

This is now fixed in PowerToys 0.14.0 https://github.com/microsoft/PowerToys/releases

@crutkas crutkas closed this as completed Dec 2, 2019
ironyman pushed a commit to ironyman/PowerToys that referenced this issue Feb 17, 2025
@zadjii-msft
Add a page for searching for extensions on winget (microsoft#369)
621044f 
Tested with the `command-line` tag, because there's no extensions in winget until microsoft/winget-pkgs#216685 merges

Also adds a link to search in the Store, though I think that won't be as useful. 

Lastly - also actually fixes the tag search 😅

Builds on microsoft#356
Closes microsoft#89
Probably needs microsoft#370 to feel right
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue-Bug Something isn't working Product-FancyZones Refers to the FancyZones PowerToy Resolution-Fix Committed Fix is checked in, but it might be 3-4 weeks until a release.
Projects
None yet
Milestone
0.14
Development

No branches or pull requests
3 participants
@crutkas @enricogior @wilhelmmedetz