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 hotkeys to change layouts doesn't respect mouse cursor #24240

Closed
dsmaher opened this issue Feb 21, 2023 · 6 comments
Closed

FancyZones hotkeys to change layouts doesn't respect mouse cursor #24240

dsmaher opened this issue Feb 21, 2023 · 6 comments
Labels
Issue-Bug Something isn't working Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something Status-No recent activity no activity in the past 5 days when follow up's are needed

Comments

@dsmaher
Copy link

dsmaher commented Feb 21, 2023

Microsoft PowerToys version

0.67.1

Installation method

WinGet

Running as admin

Yes

Area(s) with issue?

FancyZones

Steps to reproduce

I'm using 3 monitors, and when I have my mouse on either of the ones that are not the primary screen, using a hotkey (ctrl-win-alt-2 for example) will set that FancyZones layout on both of the secondary monitors. This was working properly in prior versions. Manually setting the layout using Layout editor works properly.

✔️ Expected Behavior

Only the monitor with the mouse would get the layout selected using the hotkey.

❌ Actual Behavior

Secondary monitors have the same layout applied.

Other Software

No response

@dsmaher dsmaher added Issue-Bug Something isn't working Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams labels Feb 21, 2023
@dsmaher
Copy link
Author

dsmaher commented Feb 21, 2023

...and now that I've used the layout editor to select layouts (and submitted this bug)... the hotkeys are working properly. 🤷

So... maybe it was a problem with internal inconsistency with saved data that got fixed by using the layout editor?

I'll leave this open for a day or two in case it comes back, but otherwise it seems "fixed" for now.

@dsmaher
Copy link
Author

dsmaher commented Feb 24, 2023

This hasn't reappeared and I only saw it on one of my machines so probably not something to worry about.

@dsmaher dsmaher closed this as completed Feb 24, 2023
@dsmaher
Copy link
Author

dsmaher commented Mar 17, 2023

Ok, this has reappeared multiple times whenever I restart. And, I think I know what might be the reason this is happening. The machine this occurs on is on the Insider Beta channel. When I fix it by using the layout editor, it's no longer a problem until the next reboot. But once I reboot, the zones are wrong on the non-primary monitors and I have to fix it again.

FYI - this also happens with 0.68.1.

@dsmaher dsmaher reopened this Mar 17, 2023
@dsmaher
Copy link
Author

dsmaher commented Apr 7, 2023

Still an issue with 0.69.0. I am currently on Insider Beta channel build 22624.1537, if that's helpful.

@cinnamon-msft
Copy link
Collaborator

Are you still experiencing this issue? /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 Status-No recent activity no activity in the past 5 days when follow up's are needed and removed Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams labels Oct 29, 2024
Copy link
Contributor

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 5 days. It will be closed if no further activity occurs within 5 days of this comment.

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-Author-Feedback The original author of the issue/PR needs to come back and respond to something Status-No recent activity no activity in the past 5 days when follow up's are needed
Projects
None yet
Development

No branches or pull requests

2 participants