From ffac28eb7eed2e3de1754ecf2f234fe1078b5871 Mon Sep 17 00:00:00 2001 From: LGUG2Z Date: Wed, 28 Oct 2026 22:17:46 -0700 Subject: [PATCH] docs(platform): own-window exclusion and ghost tiles on KDE --- docs/PLATFORM.md | 4 ++-- docs/dev/kde-checkpoints.md | 6 ++++-- 2 files changed, 6 insertions(+), 4 deletions(-) diff --git a/docs/PLATFORM.md b/docs/PLATFORM.md index f8c4b861..a1217b38 100644 --- a/docs/PLATFORM.md +++ b/docs/PLATFORM.md @@ -160,10 +160,10 @@ KDE. What is written from the sources and has not been seen to work on a real Pl | the window track | komorebi for KDE's own state: a Wayland client cannot list other programs' windows, so only windows komorebi manages are listed, each shown when its workspace is showing and it is in front of its stack | | komorebi's sockets | `$XDG_RUNTIME_DIR/komorebi/` (the command socket `komorebi.sock` and the subscribers'), and the data directory where there is no runtime directory | | komorebi's log | `~/.local/share/komorebi/komorebi_plaintext.log.`; the span of an event's handler is `handle_event` and of a command's `process_command` | -| the program's own windows | not left out of the video: the compositor's screencast of an output has every window on it. komorebi is told to ignore them by their application id, `komorebic ignore-rule class komorebi-recorder`, run before the window exists | +| the program's own windows | left out of the video by a KWin window rule (`excludefromcapture`, forced for the window class `komorebi-recorder`), which `record` writes to `~/.config/kwinrulesrc` and has KWin read; komorebi is told to ignore them by their application id, `komorebic ignore-rule class komorebi-recorder`, run before the window exists. Whether KWin honours the rule for a screencast of an output is a check still to make (K3) | | the window's application id | the window's application id is `komorebi-recorder`, which is the `class` komorebi for KDE sees | | `--probe-windows` | Windows only | -| ghost tiles | not found: they need the Windows probe or a picture of the screen read for them, and neither is written for KDE | +| ghost tiles | found from the frames komorebi has in its state, as on a Mac (a window in front on a showing workspace that has no frame anyone can see). No rule is proposed for one: komorebi for KDE's rules are in its own repository | komorebi for KDE's rules are checked against the log and the events of a running komorebi (`komorebi --fake-backend`, an in-memory desktop with no windows), and against its source. They are not checked against a recording of a real diff --git a/docs/dev/kde-checkpoints.md b/docs/dev/kde-checkpoints.md index 376fdea6..887f7f75 100644 --- a/docs/dev/kde-checkpoints.md +++ b/docs/dev/kde-checkpoints.md @@ -83,8 +83,10 @@ Status: not run. 1. `komorebi-recorder` with no command opens the window. Expect it to be titled `komorebi-recorder` and not tiled. 2. If it was tiled, `komorebic ignore-rule class komorebi-recorder` was not applied in time, or the window's class is not what is expected: `komorebic state` says what the window's class is. -3. The window is in the video of the screen. Whether that matters, and whether a screencast of the other windows only is - wanted, is open (`stream_window` of the protocol takes one window). +3. `record` writes a KWin window rule (`~/.config/kwinrulesrc`, group `komorebi-recorder-exclude-from-capture`) that + forces `excludefromcapture` for the class `komorebi-recorder`. Record with the window open and play the video: the + window should not be in it. If it is, say whether `kwinrulesrc` has the rule, whether System Settings > Window + Rules shows it, and what `qdbus6 org.kde.KWin /KWin supportInformation` says of the window's class. ## K4: the OS trace and the window track