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 #34625

Closed
mollac opened this issue Sep 5, 2024 · 8 comments
Closed

Fancy Zones #34625

mollac opened this issue Sep 5, 2024 · 8 comments
Labels
Issue-Bug Something isn't working Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams Product-Workspaces Refers to the Workspaces utility

Comments

@mollac
Copy link

mollac commented Sep 5, 2024

Microsoft PowerToys version

0.84.0

Installation method

PowerToys auto-update

Running as admin

Yes

Area(s) with issue?

FancyZones

Steps to reproduce

Hold SHIFT while dragging window.

✔️ Expected Behavior

window snaps to fancy zone

❌ Actual Behavior

Can't see any zones, window can't snap to anything.

Other Software

No response

@mollac mollac added Issue-Bug Something isn't working Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams labels Sep 5, 2024
Copy link

We've found some similar issues:

If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.

Note: You can give me feedback by 👍 or 👎 this comment.

@paudefuente
Copy link

I also have the same error. Same PowerToys version and exactly same error: shift key doesn't activate the predefined zones.

@paudefuente
Copy link

I also have the same error. Same PowerToys version and exactly same error: shift key doesn't activate the predefined zones.

I've also noticed that it happens with Workzone's preloaded windows. I don't know if it's because they are inactive somehow.

@gideonstar-git
Copy link

I also have the same error. Same PowerToys version and exactly same error: shift key doesn't activate the predefined zones.

I've also noticed that it happens with Workzone's preloaded windows. I don't know if it's because they are inactive somehow.

Exactly the same behaviour here. Windows created by Workzones are not recognised by Fancy Zones.

@plante-msft
Copy link
Contributor

@mollac is this happening for all Windows, or specifically for Windows created by Workspaces?

We have an issue tracking the latter #34566

@paudefuente
Copy link

@plante-msft Sorry for the late answer.

For me in particular it occurs for all the windows created by Workspace. If I close a certain windows and open it again, it works properly again!

@plante-msft
Copy link
Contributor

Thanks - figured it was the Workspaces/FancyZones bug :)

Closing as dup to track via the mega-issue.

/dup #34566

Copy link
Contributor

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-github-policy-service microsoft-github-policy-service bot added 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 Sep 17, 2024
@plante-msft plante-msft added Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams Product-Workspaces Refers to the Workspaces utility and removed Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. labels Sep 17, 2024
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-Triage For issues raised to be triaged and prioritized by internal Microsoft teams Product-Workspaces Refers to the Workspaces utility
Projects
None yet
Development

No branches or pull requests

4 participants