mirror of
https://github.com/LGUG2Z/komorebi.git
synced 2026-11-16 22:01:22 +01:00
docs(scrolling): the scrolling layout, and what changed in the design docs
docs/usage/scrolling-layout.md says how the columns work. The design docs say what the strip is, where a window out of view rests, and that the generated tables of COMPARE.md are to be made again.
This commit is contained in:
1 parent
e42a86454c
commit
76c97fb4e1
9 files changed
+265
-38
No files matched your search
+4
-3
@@ -219,9 +219,10 @@ to the module that breaks how komorebi is installed or started fails the VM suit
|
||||
|
||||
KWin moves a window anywhere it is asked to, but when it resizes a window it keeps 100 pixels of
|
||||
it on an output, and it does so once the client has drawn at the new size, which is after the
|
||||
bridge has set the frame. The scrolling layout moves the windows of the columns out of view off
|
||||
the screen and resizes them in the same command, and a terminal that rounds its size to its
|
||||
cells is resized again by its client, so KWin pulls both back onto the screen. By then, setting
|
||||
bridge has set the frame. The scrolling layout moves the windows of the columns out of view to the
|
||||
edge of the work area, where a few pixels of them are on the screen, and resizes the ones that
|
||||
change width in the same command, and a terminal that rounds its size to its cells is resized
|
||||
again by its client, so KWin pulls both back onto the screen. By then, setting
|
||||
the position alone is a plain move, which KWin honors. The bridge remembers where it was asked
|
||||
to put a window for a second, and sets the position again when the window's frame changes to
|
||||
another one in that time ([PLATFORM.md](PLATFORM.md#how-clients-answer-a-frame)). Three tries
|
||||
|
||||
Reference in new issue
Block a user