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

Default FancyZones layout not being respected #24817

Closed
ralphsmith80 opened this issue Mar 14, 2023 · 8 comments
Closed

Default FancyZones layout not being respected #24817

ralphsmith80 opened this issue Mar 14, 2023 · 8 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 Resolution-Can't Repro Couldn't reproduce the issue on the most recent code path

Comments

@ralphsmith80
Copy link

ralphsmith80 commented Mar 14, 2023

Microsoft PowerToys version

0.68.1

Installation method

PowerToys auto-update

Running as admin

Yes

Area(s) with issue?

FancyZones

Steps to reproduce

  1. Change the default layout to Columns.
    image
  2. Let computer go to sleep.
  3. Wake computer
  4. Layout is set to Priority Grid

Launching the layout editor opens with the expected layout, but it does not take affect even after reselecting the Columns layout. The only way I've found to get back to the Column layout is to use the task manager to end the PowerToys.Runner process and restart it.

✔️ Expected Behavior

Default layout to be used when computer wakes.

❌ Actual Behavior

Priority Grid layout is used.

Other Software

No response

@ralphsmith80 ralphsmith80 added Issue-Bug Something isn't working Needs-Triage For issues raised to be triaged and prioritized by internal Microsoft teams labels Mar 14, 2023
@stefansjfw
Copy link
Collaborator

Hi, thanks for reaching out. Could you attach /bugreport? Thanks

@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 Mar 22, 2023
@microsoft-github-policy-service
Copy link
Contributor

Hi there!

We need a bit more information to really debug this issue. Can you add a "Report Bug" zip file here? You right click on our system tray icon and just go to report bug. Then drag the zipfile from your desktop onto the GitHub comment box in this issue. Thanks!
Report Bug

@stefansjfw stefansjfw added the Product-FancyZones Refers to the FancyZones PowerToy label Mar 22, 2023
@ralphsmith80
Copy link
Author

ralphsmith80 commented Mar 23, 2023

hmm, didn't get a notification for this. Anyway, found out some more info. When this issue occurs, I see multiple Power Toys icons in the system tray icon area. If I exit one, all (three) go away and restarting Power Toys resumes working. I'm pretty sure I tried this before, but I don't recall seeing multiple Power Toys icons in that case.

PowerToysReport_2023-03-23-17-05-43.zip

@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 Mar 23, 2023
@ralphsmith80
Copy link
Author

As an update to what I mentioned in my last update. It looks like usually there is only one Power Toys icon in the system tray area and exiting that and restarting Power Toys gets it back to the normal state.

The workaround is easier than what I originally described, but still annoying to have to do that every time you wake up the computer.

@MacelinCane
Copy link

MacelinCane commented May 6, 2023

Hi. I have the same experience exactly, and I've attached a bug report as well. 3 actually, because I only just learned that clicking Bug Report wasn't automatically sending something to you. :)
Version v0.69.1
Hope this helps. LOVE PowerToys!

PowerToysReport_2023-05-04-09-04-21.zip

PowerToysReport_2023-05-05-22-07-06.zip

PowerToysReport_2023-05-05-22-05-47.zip

@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 and removed 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 labels Oct 29, 2024
@ralphsmith80
Copy link
Author

No, I don't think this is still an issue.

@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 Oct 29, 2024
@cinnamon-msft cinnamon-msft added the Resolution-Can't Repro Couldn't reproduce the issue on the most recent code path label Oct 30, 2024
@gizmo2501
Copy link

gizmo2501 commented Jan 7, 2025

This is still an issue. I am getting this on 0.87.1.

I have to open FancyZones layout editor to make it respect my defaults I have set.

PowerToysReport_2025-01-07-17-21-44.zip

#36729

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 Resolution-Can't Repro Couldn't reproduce the issue on the most recent code path
Projects
Development

No branches or pull requests

5 participants