Multi monitor arrangement

[bedge]

I'm working with a stable config and don't need dynamic monitor cfg changes.
I've watched vids and read docs/threads and there some info I just can't find:

1. How/where/why to reference the display_index_preferences in the monitor array. And what exactly does "monitor preference" mean?

2. How to describe the physical monitor placement. I saw there's are window_based_work_area_offset and window_based_work_area_offset_limit elements, but not a great description of how these are used.

3. What's the difference between:
   monitor_index_preferences vs display_index_preferences?
   And, what are they used for?

These do not help the user with the setup:

In short, how do I replicate this info in the komorebi.json:

given:

❯ komorebic monitor-information
{
  "AUO87A8-5&1e786be3&0&UID4354": {
    "left": 0,
    "top": 1440,
    "right": 2560,
    "bottom": 1440
  },
  "HPN349B-5&1e786be3&0&UID4357": {
    "left": 0,
    "top": 0,
    "right": 2560,
    "bottom": 1440
  },
  "HPN349B-5&1e786be3&0&UID4356": {
    "left": -1440,
    "top": 0,
    "right": 1440,
    "bottom": 2560
  }
}

From the image:
1 = laptop display: "HPN349B-5&1e786be3&0&UID4357"
2 = HP widescreen, vertical
3 = HP widescreen

3. What do I need

  "display_index_preferences": {
    "0": "HPN349B-5&1e786be3&0&UID4357",
    "1": "AUO87A8-5&1e786be3&0&UID4354",
    "2": "HPN349B-5&1e786be3&0&UID4356"
  },

for ?
Do those indexes need to be referenced elsewhere?

The monitors arary docs there's the text "Monitor-specific work area offset (default: None)"
and one needs to provide a bottom, left, right and top.
units?
base?
offset?
where's the origin, bottom left, top left, or?

Yes, it does expand to say "The left point in a Win32 Rect", but that's a developer POV, not a users.

Maybe one could add an "identify monitor & offset" as a komorebi command?
Such that one could iterate on tweaking the cfg and running the "show me the effective monitor cfg" and see the changes on screen to see if it matched expectations. Sort of line the windows monitor cfg "identify" button.
It would be better than "that's not right and I've no idea how it's being interpreted, only that it's wrong".

Thanks in advance

[LGUG2Z]

Generally unless you need to force a different monitor order than the order that Windows assigns, you don't need to worry about either of these options.

Sometimes people will have three monitors in a row (for example) monitor 1 | monitor 2 | monitor 3 but Windows will assign them index orders that don't match this.

monitor_index_preferences is used try to identify a monitor by its size, while display_index_preferences is used to try and identify a monitor by its identifier (not all monitors return identifiers, which is why both options are available).

How to describe the physical monitor placement

There is no way to describe this (ie. up/down/left/right relationships between monitors) - the operating system stores all monitors in a list, which is why komorebi does the same.

Do those indexes need to be referenced elsewhere?

To break down the snippet you pasted:

    "0": "HPN349B-5&1e786be3&0&UID4357",

"If there is a monitor with the ID HPN349B-5&1e786be3&0&UID4357 known to the operating system, apply the settings from monitors[0] in komorebi.json to that monitor.

    "1": "AUO87A8-5&1e786be3&0&UID4354",

"If there is a monitor with the ID AUO87A8-5&1e786be3&0&UID4354 known to the operating system, apply the settings from monitors[1] in komorebi.json to that monitor.

    "2": "HPN349B-5&1e786be3&0&UID4356"

"If there is a monitor with the ID HPN349B-5&1e786be3&0&UID4356 known to the operating system, apply the settings from monitors[2] in komorebi.json to that monitor.

I saw there's are window_based_work_area_offset and window_based_work_area_offset_limit elements, but not a great description of how these are used.

This is an option for restricting the area in which komorebi will tile windows on the screen - mostly used by people who have super ultrawide monitors who don't want tiling to take up the full width of the screen when only a single window is open (especially useful with apps that have most of their UI elements on the left and hardly any on the right), for example:

[bedge]

Regarding:

There is no way to describe this (ie. up/down/left/right relationships between monitors) - the operating system stores all monitors in a list, which is why komorebi does the same.

It appears to work given:

• focus left from the left side of 1 or 3 navigates to 2
• focus down from 3 goes to 1
• focus down from 1 does nothing
• focus up from 2 or 3 do nothing
• focus right from 2 goes to 3 because there's more of 3 along the long side of 2 than there is of 1.

It's hard to argue with the behavior. I'd claim it works :)

[bedge]

All working now. resolving.
My issue was thinking that somehow the display_index_preferences indeces needed to be referenced in the monitors [] array.