aboutsummaryrefslogtreecommitdiffstats
path: root/docs/scripting.md
diff options
context:
space:
mode:
authoruser <user@clank>2026-08-14 19:39:32 +0200
committeruser <user@clank>2026-08-14 19:39:32 +0200
commit277869e7621b057554f6c02c478c4786392e0aa4 (patch)
tree898724582d90185dd06e6aaafdd476f6fd380dd9 /docs/scripting.md
parentsl0ppty: one save, one reload (diff)
downloadslosh-277869e7621b057554f6c02c478c4786392e0aa4.tar.gz
slosh-277869e7621b057554f6c02c478c4786392e0aa4.tar.xz
slosh-277869e7621b057554f6c02c478c4786392e0aa4.zip
sl0ppty: zoom a pane, and give the frame buttons for it
A pane can now fill its tab and go back again, by C-a z or by a button in the frame's top-right corner. The others keep running; they are just not drawn. Zoom is intent rather than derived state, so it is stored like focus is: on the tab, one per tab, because zooming a pane in one tab has nothing to say about another. Everything else about it falls out of that. It survives the layout being recomputed because it is an input to the layout rather than a product of it. It cannot outlive the pane it names, because the id is checked against the tree every pass and dropped if the pane has gone. And it needed no new arrangement: "show this one and nothing else" is what layout_solo already did for a tab too small to divide, and zoom is the same shape asked for on purpose rather than as a last resort. The frame gets buttons back, having had its split button removed once already on the grounds that one glyph cannot mean four directions. Zoom and close are two verbs a single glyph *can* mean, which is the difference; splitting is still done by clicking an edge, where the edge encodes the direction. They cost six columns of every frame, which is a real tax and why pane_buttons turns them off — the keybindings are untouched by that, because the setting is about the affordance and not the verb. A test in the split-UX suite had been asserting that the frame spends nothing on buttons. It now asserts the weaker thing with them on and the original, stronger thing with them off, which says what actually changed rather than lowering a number until it passed. One test of mine was wrong in an instructive way: it counted visible panes across every tab, and panes in a tab that is not on screen were never laid out, so they carry whatever rect and hidden flag they had last time. The comment on those fields says exactly that. It counts the current tab now.
Diffstat (limited to 'docs/scripting.md')
0 files changed, 0 insertions, 0 deletions