mirror of
https://github.com/LGUG2Z/komorebi.git
synced 2026-11-15 13:22:19 +01:00
LGUG2Z
3cc8ff63b3
enforce_resize_for_right_vertical_stack said "Zero is actually on the right" but locked top, bottom and right of resize_dimensions[1], so the main container (index 0, drawn on the right: arrangement.rs primary_left = area.right - primary_width) was never constrained and the first stack container could not be resized at all. Index 0 now loses top, bottom and right (it can only grow to the left); the stack loop over [1..] is unchanged (nothing in it goes left, first not up, last not down). The test that pinned the buggy result is replaced by the previously ignored test of the intended behaviour, un-ignored and extended to 1 to 4 tiles: [l, rb], [l, rb, tr], [l, rb, trb, tr]. BEHAVIOUR (all three daemons share this function): resizing in the right-main-vertical-stack layout changes. Gate: Windows e2e resize scenarios; the ones that run in right-main-vertical-stack are none by name (resize_commands uses the default layout; layouts.py and commands.py only tile and cycle through right-main-vertical-stack), so a pointer or resize-edge scenario in that layout would need adding. Verified: cargo test -p komorebi-core, with and without --features schemars, all pass; no e2e run.