docs(repo): the ledger and the scenario table for monitors and layout_flip

Both are new shared scenarios and have not been run on a real KWin or Windows
guest yet, so their columns say so.
This commit is contained in:
LGUG2Z committed 2026-10-30 12:51:06 -07:00
1 parent b8be236f98
commit 26b4ff931b
2 files changed
+26

No files matched your search

+2
View File
@@ -60,6 +60,8 @@ runs, and goes stale when the code changes.
| `pausing` | a paused daemon leaves a new window alone, and an unpaused one takes the next | pass | pass |
| `tiling_off` | `toggle-tiling` leaves the windows where they are, a layout change moves none, and tiling again tiles them | pass | pass |
| `scrolling` | in the scrolling layout each window in turn has the focus and is inside the work area | pass | pass |
| `monitors` | the monitor commands (`send-to-monitor`, `move-to-monitor`, their cycle, workspace and named forms, `focus-monitor`, `cycle-monitor`, `focus-monitor-workspace`, `cycle-move-workspace-to-monitor`, `focus-monitor-at-cursor` where there is a pointer) put each window on the monitor and workspace asked for, tiled in its display, and the focus where each leaves it | not run | not run |
| `layout_flip` | `layout_flip` in the config (`Horizontal`, `Vertical`, `HorizontalAndVertical`) mirrors a workspace's layout from the start, `flip-layout` turns it off and on, and it is the named workspace's own | not run | not run |
`rules` passes on kfde in every check. One run of the suite that holds it also failed a check that
is not the scenario's, that the daemon had exited after `komorebic stop`; the next run passed it,
+24
View File
@@ -141,6 +141,30 @@ daemon with none.
| 4, by the app id (`Class`), by the title, and after the one in focus | extra `by_app_id` (the shared scenario matches by title only; a candidate for it) |
| 5, `Exe` `foot.exe` matches `foot` | extra `by_program` (KDE: no `.exe` on this port) |
## monitors and layout_flip
Two shared scenarios for gaps no Rust test covers either, in `core-e2e`. Nothing was dropped: the
sweep's multi-monitor commands (`commands`) still only say the daemon stays healthy, and these say
what each does.
- `monitors` (needs two displays; one is plugged in if there is one, and out again) opens four
windows and checks, from the OS and the daemon's state, `send-to-monitor`, `move-to-monitor`,
their `cycle-` forms, the `-monitor-workspace` forms, `send-to-named-workspace`,
`move-to-named-workspace`, `focus-monitor`, `cycle-monitor`, `focus-monitor-workspace` and
`cycle-move-workspace-to-monitor`: each window on the monitor and workspace asked for, the others
where they were, tiled inside the display of their monitor (read from `displays()`, which may
differ in size), and the focus where the command leaves it (a send keeps it, a move takes it).
`monitors.at_cursor` is `focus-monitor-at-cursor`, and runs only where `has("pointer")`.
The suite starts KWin with two outputs and unplugs the second before the daemon starts, so that
every other scenario still sees one display.
- `layout_flip` starts the daemon with the workspace option set (`Horizontal`, `Vertical`,
`HorizontalAndVertical`) over columns, rows and BSP with two and three windows, checks the
mirror from the OS, that `flip-layout` turns the option off and on, that a command adds the other
axis, and that the option is the named workspace's own.
Neither has been run on a real KWin or Windows guest yet; the fake in `tests/fake_desk.py` stands in
for the unit tests (`tests/test_monitors.py`).
## workspace-switch
Nearly everything this suite checks is KWin's: a workspace is a virtual desktop. The shared