Powertoys: FancyZones not accepting Layout/Grid on secondary Monitor

Created on 7 Dec 2020  ·  18Comments  ·  Source: microsoft/PowerToys

ℹ Computer information

  • PowerToys version: 0.28
  • PowerToy Utility: FancyZones
  • Running PowerToys as Admin: Yes
  • Windows build number: 20H2 19042.630
  • Dell XPS15 7590
  • Dell TB16 Dockingstation
  • Samsung 4k 28"
  • 4K 100% Scale
  • Only Secondary Monitor (Notebook Display is off)

📝 Provide detailed reproduction steps (if any)

  1. Hold shift and drag window
  2. Three-Row-Layout appears
  3. Change to 0-5 Rows, still shows 3 on drag
  4. Custom Layouts are also not shown

✔️ Expected result

Custom Layout is shown or changes within the settings (Row-Count) should be shown

❌ Actual result

Always only 3-Row-Layout is visible

📷 Screenshots

_Are there any useful screenshots? WinKey+Shift+S and then just paste them directly into the form_
image
image
image

Issue-Bug Product-FancyZones Resolution-Duplicate

Most helpful comment

I was able to work around this problem by manually editing the %LocalAppData%\Microsoft\PowerToys\FancyZones\zones-settings.json. The devices array has two elements, one for each of the two displays I have. The FancyZones editor kept changing the active-zoneset of display 1 when I was using display 2 only. I had to change the active-zoneset manually to apply the layout I wanted to the display I actually use.

  "devices": [
    {
      "device-id": "GSM5B09#4&17a0b355&0&UID224795_3840_2160_{00000000-0000-0000-0000-000000000000}",
      "active-zoneset": {
        "uuid": "{750F4B18-EDC6-4D6C-B1B4-02F2D2BCB801}",
        "type": "custom"
      },
      "editor-show-spacing": true,
      "editor-spacing": 16,
      "editor-zone-count": 3,
      "editor-sensitivity-radius": 20
    },
    {
      "device-id": "SEC3542#4&17a0b355&0&UID265988_3840_2160_{00000000-0000-0000-0000-000000000000}",
      "active-zoneset": {
        "uuid": "{750F4B18-EDC6-4D6C-B1B4-02F2D2BCB801}",
        "type": "custom"
      },
      "editor-show-spacing": true,
      "editor-spacing": 16,
      "editor-zone-count": 3,
      "editor-sensitivity-radius": 20
    }
  ],

All 18 comments

Sorry, but this is simply another issue, not the same like in #8330. #8330 happened for me after a lockscreen, which i resolved by restarting PowerToys. This is a different thing, the Layout simply keeps being a 3-Row-Layout, even with Custom Layouts or different count of Rows.

Sorry, but this is simply another issue, not the same like in #8330. #8330
happened for me after a lockscreen, which i resolved by restarting
PowerToys. This is a different thing, the Layout simply keeps being a
3-Row-Layout, even with Custom Layouts or different count of Rows.

--
Mit freundlichen Grüßen

Danial Barazandehpay


Mob. +49 (151) 401 775 30
Mail: d.[email protected]

Am Mo., 7. Dez. 2020 um 21:37 Uhr schrieb Enrico Giordani <
[email protected]>:

@dbara https://github.com/dbara
tracked in #8330 https://github.com/microsoft/PowerToys/issues/8330


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/PowerToys/issues/8460#issuecomment-740165835,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAUW5EXYY3YHIE4QQ6ASRKDSTU4HNANCNFSM4UQ7EVDA
.

I have the same problem, regardless of what settings I actually make, I am stuck with the same 3 column layout like in the screen shots. Have reinstalled and reset options but problem remains.

I was able to work around this problem by manually editing the %LocalAppData%\Microsoft\PowerToys\FancyZones\zones-settings.json. The devices array has two elements, one for each of the two displays I have. The FancyZones editor kept changing the active-zoneset of display 1 when I was using display 2 only. I had to change the active-zoneset manually to apply the layout I wanted to the display I actually use.

  "devices": [
    {
      "device-id": "GSM5B09#4&17a0b355&0&UID224795_3840_2160_{00000000-0000-0000-0000-000000000000}",
      "active-zoneset": {
        "uuid": "{750F4B18-EDC6-4D6C-B1B4-02F2D2BCB801}",
        "type": "custom"
      },
      "editor-show-spacing": true,
      "editor-spacing": 16,
      "editor-zone-count": 3,
      "editor-sensitivity-radius": 20
    },
    {
      "device-id": "SEC3542#4&17a0b355&0&UID265988_3840_2160_{00000000-0000-0000-0000-000000000000}",
      "active-zoneset": {
        "uuid": "{750F4B18-EDC6-4D6C-B1B4-02F2D2BCB801}",
        "type": "custom"
      },
      "editor-show-spacing": true,
      "editor-spacing": 16,
      "editor-zone-count": 3,
      "editor-sensitivity-radius": 20
    }
  ],

I was able to work around this problem by manually editing the %LocalAppData%\Microsoft\PowerToys\FancyZones\zones-settings.json. The devices array has two elements, one for each of the two displays I have. The FancyZones editor kept changing the active-zoneset of display 1 when I was using display 2 only. I had to change the active-zoneset manually to apply the layout I wanted to the display I actually use.

  "devices": [
    {
      "device-id": "GSM5B09#4&17a0b355&0&UID224795_3840_2160_{00000000-0000-0000-0000-000000000000}",
      "active-zoneset": {
        "uuid": "{750F4B18-EDC6-4D6C-B1B4-02F2D2BCB801}",
        "type": "custom"
      },
      "editor-show-spacing": true,
      "editor-spacing": 16,
      "editor-zone-count": 3,
      "editor-sensitivity-radius": 20
    },
    {
      "device-id": "SEC3542#4&17a0b355&0&UID265988_3840_2160_{00000000-0000-0000-0000-000000000000}",
      "active-zoneset": {
        "uuid": "{750F4B18-EDC6-4D6C-B1B4-02F2D2BCB801}",
        "type": "custom"
      },
      "editor-show-spacing": true,
      "editor-spacing": 16,
      "editor-zone-count": 3,
      "editor-sensitivity-radius": 20
    }
  ],

Wow, that dit it. Works like a charm now. Thanks a lot.

I found that the problem here seem to be having attached but disabled monitors. If I enable the second monitor (the laptop screen) I now get further options in Fancy Zone editor that is not there if only one monitor is enabled. Seems like it might default to the first monitor with disabled monitors rather than the one actually enabled. It appears that if you enable all monitors, set up zones for the monitor/monitors that you want enabled and then disable the ones you dont want enabled, the settings stick. Regardless, this is a bug that needs fixing as most users probably never will be able to find this out or bother with it.

@improwise
if you have an attached and disabled monitor, the tracking issue is https://github.com/microsoft/PowerToys/issues/8339
0.27.1 will fix it.

I found that the problem here seem to be having attached but disabled monitors. If I enable the second monitor (the laptop screen) I now get further options in Fancy Zone editor that is not there if only one monitor is enabled. Seems like it might default to the first monitor with disabled monitors rather than the one actually enabled. It appears that if you enable all monitors, set up zones for the monitor/monitors that you want enabled and then disable the ones you dont want enabled, the settings stick. Regardless, this is a bug that needs fixing as most users probably never will be able to find this out or bother with it.

Yeah, I alreday thought about that, seems to be the issue. It saves the settings always for the first monitor, if one is disabled.

@improwise
if you have an attached and disabled monitor, the tracking issue is #8339
0.27.1 will fix it.

I don't think so. For me he has the same issue, because of the fist monitor being disabled.

@dbara
#8339 is tracking the problem that happens when the built-in monitor disabled.
So what is the thing that "you don't think so"?

@dbara

8339 is tracking the problem that happens when the built-in monitor disabled.

So what is the thing that "you don't think so"?

Whoa, why so agressive? The issue is different even if the given facts are similar. There is a difference between "apply does not seem to accept klick" and "layout is saved for wrong monitor", don't you think?

@dbara

Whoa, why so agressive?

Is just a question to understand what you were referring to.

There is a difference between "apply does not seem to accept klick" and "layout is saved for wrong monitor", don't you think?

The problem in #8339 is that the layout is saved for the wrong monitor. Aren't you experiencing the same thing?

@improwise
if you have an attached and disabled monitor, the tracking issue is #8339
0.27.1 will fix it.

Based on title it seems to be different, but based on a quick look at the contents, it seems to be related. Since the other monitor is disabled, its hard to see if it applied there instead (and if it is enabled when editing zones the bug does not show up). Anyhow, it would seem likely that they are related and probably part of the same problem.

@dbara

Whoa, why so agressive?

Is just a question to understand what you were referring to.

There is a difference between "apply does not seem to accept klick" and "layout is saved for wrong monitor", don't you think?

The problem in #8339 is that the layout is saved for the wrong monitor. Aren't you experiencing the same thing?

Well then either the description isn't the best or I still don't get it. For me #8339 is about the Save-Button which doesn't work, in this case it works but simply saves the desired/created layout for the wrong monitor.

@improwise
if you have an attached and disabled monitor, the tracking issue is #8339
0.27.1 will fix it.

Based on title it seems to be different, but based on a quick look at the contents, it seems to be related. Since the other monitor is disabled, its hard to see if it applied there instead (and if it is enabled when editing zones the bug does not show up). Anyhow, it would seem likely that they are related and probably part of the same problem.

I agree, I should have read more. Time is flying ;)
Could these two be merged? I believe the screenshots here may be helpful for other people and the workaround works like a charm

@improwise
if you have an attached and disabled monitor, the tracking issue is #8339
0.27.1 will fix it.

Based on title it seems to be different, but based on a quick look at the contents, it seems to be related. Since the other monitor is disabled, its hard to see if it applied there instead (and if it is enabled when editing zones the bug does not show up). Anyhow, it would seem likely that they are related and probably part of the same problem.

I agree, I should have read more. Time is flying ;)
Could these two be merged? I believe the screenshots here may be helpful for other people and the workaround works like a charm

Would imagine that the problem is quite clear by now, that a check should be made sure to check active state of monitors and make sure to pick the right one. Have not looked at the code but would imagine that it is quite an easy fix once the problem has been identified. Good that the work around seem to work meanwhile, I have my zones back now after some additional tinkering :)

@dbara @improwise
closing this as duplicate of #8339
The bug has been already fixed and the fix will be available in 0.27.1

Was this page helpful?
0 / 5 - 0 ratings