aboutsummaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authoruser <user@clank>2026-08-14 20:55:02 +0200
committeruser <user@clank>2026-08-14 20:55:02 +0200
commit5a15f9519554e8e736955a1900f7bdffc79603a0 (patch)
tree0921187e8017ef5ba8a43ae72c787dd0bcc617f2 /docs
parentsl0ppty: every place the boundaries meet is a crossing (diff)
downloadslosh-5a15f9519554e8e736955a1900f7bdffc79603a0.tar.gz
slosh-5a15f9519554e8e736955a1900f7bdffc79603a0.tar.xz
slosh-5a15f9519554e8e736955a1900f7bdffc79603a0.zip
sl0ppty: find the crossing whichever way the tree is nested
Half the crossings were invisible, and it was the half that depends on how you built the layout rather than on how it looks. Rows of columns gives a full-width row boundary with column boundaries running into it from above and below. Columns of rows gives a full-height column boundary with row boundaries running into it from the sides. On screen these are the same picture; in the tree they are opposite, and the adjacency test only looked for the first — two gaps touching side to side never matched, so a layout built by splitting the other way round had no crossings at all. The test is now that the two touch, in either axis. The crossing itself was never in doubt: it is the column boundary's columns by the row boundary's rows, which is the same cell either way. Corners now hold up to two boundaries of each kind rather than two column ones and a single row one. That asymmetry was an artefact of only ever having seen the first nesting — in the second it is two row boundaries that can line up and need to move together, for exactly the reason two column boundaries did.
Diffstat (limited to 'docs')
0 files changed, 0 insertions, 0 deletions