Different Layouts per Monitor in FancyZones

[stinkingcedar]

Microsoft PowerToys version

0.60.0

Running as admin

• Yes

Area(s) with issue?

FancyZones, FancyZones Editor

Steps to reproduce

FancyZones

Open "Launch layout editor"

Click monitor 1, select layout.

Click monitor 2, select layout.

✔️ Expected Behavior

Each of my dual monitors would previously retain their own different layout.

❌ Actual Behavior

Each monitor mimicked the exact layout of the other monitor. Can't have two different layouts on each screen.

Other Software

No response

[Eric2XU]

Me too.... I think I have some data that can be helpful.

I have 4 monitors, 3 of 4 are all the same even thought the applied-layouts.json clearly has a different applied-layout/uuid defined. So why does the 4th one work? Its a different type of monitor. All of my monitors report by the tool with the exact same serial number. (See below)

All added by the editor as 2231 but in fact they are 2231, 2308, 2257

Sadly editing the file and putting the correct SN's doesnt fix it. This makes me think that the editor isnt the issue but whatever global function interpits the monitor SN must be busted. Perhaps the bug only happens when you have identical make/model (but diff serial numbers). I guess ill drop to a older version and see if it goes away, this wasnt a problem before but I rebuilt my PC today.

{
  "applied-layouts": [
    {
      "device": {
        "monitor": "AOC2402",
        "monitor-instance": "5\u00269ddbf8d\u00260\u0026UID413952",
        "serial-number": "2231",
        "virtual-desktop": "{00000000-0000-0000-0000-000000000000}"
      },
      "applied-layout": {
        "uuid": "{06024AFE-7636-4BF3-9199-FADCA1A6DE7B}",
        "type": "custom",
        "show-spacing": false,
        "spacing": 0,
        "zone-count": 3,
        "sensitivity-radius": 20
      }
    },
    {
      "device": {
        "monitor": "TCL0000",
        "monitor-instance": "5\u00269ddbf8d\u00260\u0026UID413959",
        "serial-number": "0",
        "virtual-desktop": "{00000000-0000-0000-0000-000000000000}"
      },
      "applied-layout": {
        "uuid": "{93272CCF-5B5C-4A96-B041-3819AAEEFFE6}",
        "type": "columns",
        "show-spacing": true,
        "spacing": 16,
        "zone-count": 3,
        "sensitivity-radius": 20
      }
    },
    {
      "device": {
        "monitor": "AOC2402",
        "monitor-instance": "5\u00269ddbf8d\u00260\u0026UID413957",
        "serial-number": "2231",
        "virtual-desktop": "{00000000-0000-0000-0000-000000000000}"
      },
      "applied-layout": {
        "uuid": "{4A1FBDEA-3BA6-46B6-840A-7BC71C6B44F6}",
        "type": "custom",
        "show-spacing": false,
        "spacing": 0,
        "zone-count": 4,
        "sensitivity-radius": 20
      }
    },
    {
      "device": {
        "monitor": "AOC2402",
        "monitor-instance": "5\u00269ddbf8d\u00260\u0026UID413955",
        "serial-number": "2231",
        "virtual-desktop": "{00000000-0000-0000-0000-000000000000}"
      },
      "applied-layout": {
        "uuid": "{136686AB-3D8B-48E3-A5F5-48AF08FA5DF0}",
        "type": "custom",
        "show-spacing": false,
        "spacing": 0,
        "zone-count": 5,
        "sensitivity-radius": 20
      }
    }
  ]
}

[Eric2XU]

Another update, I removed .60 with
choco uninstall powertoys
then install 59.1
choco install powertoys --version=0.59.1

Works again, its just a bug in .60

[jaimecbernardo]

Looks like a /dup #19203 ,
We released a fix for it on 0.60.1: https://github.com/microsoft/PowerToys/releases/tag/v0.60.1

[ghost]

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!