aboutsummaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authoruser <user@clank>2026-08-14 16:12:17 +0200
committeruser <user@clank>2026-08-14 16:12:17 +0200
commitb2d7da47ef233c8175e27309ab0f741949420283 (patch)
treed485554f11ba14f8f5f90bc837b6616f95d2ca37 /docs
parentsl0ppty: collapsing flattens the tree instead of nesting headers (diff)
downloadslosh-b2d7da47ef233c8175e27309ab0f741949420283.tar.gz
slosh-b2d7da47ef233c8175e27309ab0f741949420283.tar.xz
slosh-b2d7da47ef233c8175e27309ab0f741949420283.zip
sl0ppty: a tab is laid out or it is a list, never half of each
Collapsing was a local decision: the subtree that could not fit flattened and everything else carried on. In practice that produces a screen with a full-height pane on the left and a stack of headers on the right, which explains neither what just happened nor what to do about it. Seeing it is enough to know it is wrong. The question is now asked of the whole tab and answered once. If any node cannot give its children their floor, every pane in the tab becomes a row and the focused one opens below them — including the panes that would have fitted perfectly well on their own. That costs something real and it is worth being honest about it: a wide screen with one cramped column now flattens entirely, where before it would have kept the rest of the layout. The trade is that there is one collapsed state instead of a spectrum of partial ones, and a rule you can hold in your head is worth more here than squeezing the last working layout out of a bad size. Mechanically this made layout simpler rather than more complex. layout_node no longer decides anything about presentation; a node that cannot fit sets a flag and returns. Laying out happens twice — once to ask, once to do — and the probe is the real layout with resizing switched off rather than a second copy of the fitting arithmetic, because two copies of "does this fit" is exactly how the split guide and the layout would begin to disagree. The probe not resizing is the load-bearing part: a pane it lays out normally may be a header by the time the real pass runs, and a pane about to be collapsed must not be told a size it will never show.
Diffstat (limited to 'docs')
0 files changed, 0 insertions, 0 deletions