mirror of
https://github.com/LGUG2Z/komorebi.git
synced 2026-11-22 00:21:43 +01:00
feat(wm): a monitor changes size
When an output gets another resolution or scale, or a panel starts, grows or hides, the work area the layout fills is not the one komorebi tiled in, and nothing moved the windows until something else tiled them again. The bridge now sends the outputs, with their geometry and the work area of the desktop each shows, when KWin says they changed, when a dock window opens, closes or moves, and once a second, because KWin has no signal for the room a panel leaves. The table turns a monitor whose size or work area changed into a monitor notification. It is not a window event, since it is about no window: it goes to the monitor reconciliator, a thread that takes the window manager's lock as the threads of events and messages do, reads the size and work area of every monitor again and tiles the workspace in front of the focused monitor. Another monitor's windows keep their tiles until a retile. Every subscriber is notified of it, whether or not the state changed. vm-hotplug starts with the scale of one of two outputs changing under a running daemon. The VM library gets kde.outputs, which lists, disables, enables and scales outputs, for the commits that unplug and plug them.
This commit is contained in:
1 parent
c03e5d2970
commit
c8dc92a236
27 files changed
+1044
-75
No files matched your search
+15
-3
@@ -123,9 +123,11 @@ It connects to the session bus as `org.komorebi.Bridge`, writes the bridge to
|
||||
`$XDG_RUNTIME_DIR/komorebi/bridge.js`, and asks KWin to load it under the name
|
||||
`komorebi-bridge`, replacing a script of that name left by an earlier run. The script reports
|
||||
the windows and outputs it finds, and from then on every window that opens, closes, takes the
|
||||
focus, is minimized or brought back, moves or changes size, and the start and the end of every
|
||||
drag of a window by the user. The daemon waits up to 10 seconds for the first report and does
|
||||
not start without it.
|
||||
focus, is minimized or brought back, moves or changes size, the start and the end of every drag
|
||||
of a window by the user, and every change of the outputs (one that changes resolution or scale,
|
||||
and the room a panel leaves). KWin has no signal for that room, so the script looks at the
|
||||
outputs again when a dock window opens, closes or moves, and once a second. The daemon waits up
|
||||
to 10 seconds for the first report and does not start without it.
|
||||
|
||||
Before it loads the script, it turns on KWin's per-output virtual desktops in the user's
|
||||
`kwinrc` (`[Windows] PerOutputVirtualDesktops=true`), unless they are on, and asks KWin to
|
||||
@@ -427,6 +429,16 @@ and KWin's default snap zone of 10 pixels, a dragged edge once ended 9 pixels pa
|
||||
drag VM tests set KWin's snap zones to 0. The VM test `vm-drag-resize` drags edges in a Plasma
|
||||
session with a pointer device that the session node makes with uinput.
|
||||
|
||||
## Outputs that change
|
||||
|
||||
Measured by the VM test `vm-hotplug` at time of writing (2026-10-27), in a headless KWin 6.8.1
|
||||
with two outputs of 1920x1080:
|
||||
|
||||
- `kscreen-doctor output.<name>.scale.1.5` gives an output the geometry 1280x720. That is what
|
||||
the script reports and komorebi tiles in: every coordinate komorebi uses is KWin's logical
|
||||
one. At that scale `kdotool` prints window frames in fractions of a pixel (a width of
|
||||
695.3333), which the VM library rounds.
|
||||
|
||||
## How long a retile takes
|
||||
|
||||
Measured by the VM test `vm-latency` at time of writing (2026-10-27), in a headless KWin 6.8.1
|
||||
|
||||
Reference in new issue
Block a user