mirror of
https://github.com/LGUG2Z/komorebi.git
synced 2026-11-18 14:48:34 +01:00
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.
This commit is contained in:
1 parent
2afe3554ee
commit
7b8a559590
1 file changed
+4
@@ -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
|
||||
|
||||
|
||||
Reference in new issue
Block a user