From 7b8a559590d59c901190059ef8411ffb4b54dd16 Mon Sep 17 00:00:00 2001 From: LGUG2Z Date: Thu, 29 Oct 2026 08:28:08 -0700 Subject: [PATCH] docs(repo): what a daemon that starts again takes up on kfw A window kfw had cloaked is uncloaked by the stop and managed again on the first workspace. A minimized window is left minimized and is not managed. The lifecycle scenario counts only the windows in view. --- docs/dev/BEHAVIOUR.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/dev/BEHAVIOUR.md b/docs/dev/BEHAVIOUR.md index a93081b0..8ea4e9fa 100644 --- a/docs/dev/BEHAVIOUR.md +++ b/docs/dev/BEHAVIOUR.md @@ -100,6 +100,10 @@ These are differences between the ports that a scenario does not hide, and are n for windows and monitors, and kfw's has handles, so a scenario never compares them. - **State shape.** The two `komorebic state` outputs differ in how a window is written and in a few fields each. `core/snapshot.py` reads both, and its tests read a state recorded from each. +- **What a restart takes up.** `lifecycle` expects every window that was in view to be managed + again. On kfw `komorebic stop` uncloaks a window that was on another workspace, and a new daemon + manages it on the first workspace, but a minimized window stays minimized and is not taken up. + The scenario counts the windows that were in view, so it does not ask for the minimized one. ## What is not covered