The ban (`just lint`, and now the hygiene job) came from the macOS and KDE repositories and was
never applied to the Windows code, so the unified tree had sixteen uses of the macro: seven in
the Windows daemon, six in komorebi-core (written during the unification), one in the KDE
backend and two in the recorder. Each becomes eyre::Report::msg, with format! where the message
has arguments.
The workspace members, the path dependencies, the include_str! and test
fixture paths, the recorder's indexed source keys, and the Nix source
filter and path literals follow the new layout. Cargo.lock is unchanged.
The recorder is a member of the repository it indexes: each flavor is built from the
directory of its own daemon (komorebi-macos, komorebi-windows, komorebi-linux) and the shared
crates that log. The statements of the container, workspace and monitor moved into
komorebi-core, so the targets of the real log sample in the fixture are komorebi_core's.
KOMOREBI_SRC and KOMOREBI_COMMIT replace the three KOMOREBI_*_SRC variables, for a build
that is not in a checkout.
komorebi for Mac draws each border as an untitled, ordinary-level NSWindow owned by
the komorebi process. The Mac listing kept them but never set `border`, so a
recording gave an agent no way to tell a border from a window. They are now marked,
which lets `lag` compare a border with its window. `border_of` stays unset: a Mac
border does not name its window.
logind's PrepareForSleep on the system bus, and the screen saver's ActiveChanged on the session
bus, which komorebi for KDE listens to as well; GetActive says whether the screen is locked.
A Wayland client cannot list the windows of other programs, so the list is komorebi's own state:
each window with its rect and program, shown when its workspace is showing and it is in front of
its stack. --window-track is allowed on Linux.
KWin offers zkde_screencast_unstable_v1 only to a program whose desktop file lists it. The note
has the file to write, with the path of this executable in it.
The displays are the compositor's outputs, with the id komorebi for KDE gives a monitor with no
serial number. A screencast of one is a PipeWire node that pipewiresrc reads, stamped on the
master clock, into a segment written by the capture writer. KWin offers the screencast only to
a program whose desktop file asks for it, and says so when it does not.
DisplayCapture::start_with takes a function that connects a source to the frames' sink, which
also hears why a source died. Frames are placed in the file's time, logged and measured as on
Windows, a still display has its last frame repeated, and the file is fragmented H.264 written
by x264enc and mp4mux. The tests are a source of their own, and read the video back with the
decoder. The default codec on Linux is H.264.
One connection and a thread that reads its events keep the list of outputs, hotplug included,
so asking for it is cheap. A screencast of an output is KDE's zkde_screencast_unstable_v1,
which gives a PipeWire node and asks the user nothing.
A pipeline per decode, filesrc ! decodebin ! videoconvert ! videoscale ! appsink, gives BGRA
frames at the size asked for. The time of a frame is its stream time, because an MP4's edit
list puts the media time of the first frame after zero. The playback and viewer tests that
need decoded video pass on Linux.
Flavor::Kde is the flavor of a Linux host. Its rules are checked against a log and events
of komorebi for KDE's in-memory desktop, but not against a real desktop, so an analysis
of a KDE session says so. There are no ghost tiles for it yet.
The window's Wayland application id is komorebi-recorder; komorebic ignore-rule class
registers it before the window exists, as the exe rule does on Windows.