mirror of
https://github.com/LGUG2Z/komorebi.git
synced 2026-11-18 14:48:34 +01:00
feat(wm): monocle
A workspace could show its windows only side by side. Monocle gives one container the whole work area: the focused container is taken out of the workspace's containers, so the layout gives no container a tile, and the next tiling puts its window on the work area less the padding. Turning it off puts the container back at the index it came from, and the tiles come back as they were resized: the container keeps its resize adjustment, and the workspace does not shorten the list of adjustments while a monocle is on. The windows of the other containers are hidden on the parking desktop, as the windows behind the front one of a stack are, and the front window of each is shown again when the monocle is turned off or the window in monocle closes. A stack in monocle stays a stack. `komorebic toggle-monocle` turns it on and off. What focusing in a direction does meanwhile is set with `monocle-focus-behaviour` or switched with `toggle-monocle-focus-behaviour`: with `cycle` the monocle goes to the previous or the next container, with `no-op`, the default, no container is on any side and the focus falls through to the monitor on that side, where the monocle window of its workspace, if it has one, is given the focus, and the command fails where there is no monitor. A container that is moved to a monitor or sent to a workspace in monocle turns that monocle off first. `cycle-focus` always carries the monocle along. Giving the focus to another window gives it back to the monocle window, so that it stays in front. `move` and `cycle-move` are refused and `toggle-float` is ignored while a window is in monocle, since the focused container is not the window in front. The monocle container is in the state, with the index it goes back to, and a window in it that closes takes the monocle with it. komorebi/tests/monocle.rs drives it against the fake desktop, with one monitor and with two. vm-core-e2e checks in a real KWin that the focused window fills the work area, that the state has the monocle container, that toggling back restores the tile, that the cycle behavior gives another window the work area, and that the windows behind a monocle are parked, which a clean stop and the next start after a crash put right; vm-stacks checks a monocle over a stack; the vm-commands sweep runs the new commands.
This commit is contained in:
1 parent
2e439414db
commit
0d21dd332c
28 files changed
+1927
-101
No files matched your search
@@ -296,3 +296,22 @@ records a window in it before it asks the backend to hide it. What the composito
|
||||
hidden window (a minimize, a move to another desktop) is the echo of a command komorebi sent, and
|
||||
the window manager has to be able to tell that from the user's own: a window that the user
|
||||
minimizes leaves the layout, and one komorebi hid does not.
|
||||
|
||||
## Why is the monocle container not one of the containers?
|
||||
|
||||
Because a layout gives every container a tile, and the monocle container is the one that has the
|
||||
whole work area. [`Workspace::new_monocle_container`](../../komorebi/src/workspace.rs) takes the
|
||||
focused container out of the workspace's containers and remembers its index, and
|
||||
[`Workspace::update`](../../komorebi/src/workspace.rs) puts the window of the monocle container on
|
||||
the work area and gives the other containers no tile. The container is taken out and put back
|
||||
with the plain remove and insert of the ring, and not the ones that respect locked containers:
|
||||
the comments of the code say that a monocle, like a maximize, takes over the whole screen before
|
||||
it is reinserted at the same index, which is what respecting the indexes of locked containers
|
||||
needs.
|
||||
|
||||
The container keeps its resize adjustment, "because when this container is inevitably
|
||||
reintegrated, it would be weird if it doesn't go back to the dimensions it had before", and for
|
||||
the same reason `update` does not shorten the list of adjustments while there is a monocle
|
||||
container: with two containers, one of them in monocle, the list would be cut to one, and the
|
||||
adjustment of the container in monocle would be lost when it came back (the comments in
|
||||
`new_monocle_container` and `update`).
|
||||
Reference in new issue
Block a user