aboutsummaryrefslogtreecommitdiffstats
path: root/Cargo.toml
diff options
context:
space:
mode:
authoruser <user@clank>2026-08-08 20:40:12 +0200
committeruser <user@clank>2026-08-08 20:40:12 +0200
commit93b86ce0e0d2cec9750fb27075932f6bacd3055b (patch)
tree02325baecfb04fa70fdbefc84895269bfeeb6147 /Cargo.toml
parentsl0p: fix ghosting/artifacts when resizing panes with a gap (diff)
downloadsl0ppij-93b86ce0e0d2cec9750fb27075932f6bacd3055b.tar.gz
sl0ppij-93b86ce0e0d2cec9750fb27075932f6bacd3055b.tar.xz
sl0ppij-93b86ce0e0d2cec9750fb27075932f6bacd3055b.zip
sl0p: blank the padding ring too, fixing remaining resize ghosting
The previous ghosting fix only covered ONE of the two regions the insets carve out. With `padding N` there is a second unowned region: the cells between the frame border and the content rect. Nothing wrote them, so when a pane grew, cells that had previously held another pane's border or title kept those glyphs - the reported 'old pane title/border repeated in the gap space'. Both rings are now blanked at every frame-render site: 1. allocation \ drawn frame (outer gap) 2. frame inner \ content rect (inner padding) Frameless mode is explicitly excluded from ring 2. With pane frames off the cells around the content belong to ui/boundaries.rs, which draws the inter-pane boundaries there, and content_offset deliberately leaves room for them. Blanking that region erased the boundaries and broke three tests (render_stacks_without_pane_frames, swap_tiled_layout_with_stacked_children_and_no_pane_frames, send_cli_toggle_pane_frames_action). Collapsing the interior onto the content rect emits no ring at all in that mode. gap_ring_chunks is now robust to any rect relationship: spans are clamped to `outer`, so a mis-clamped caller cannot make it write outside the pane's own allocation. Tested with inner rects that cover, miss, straddle and degenerate against outer. Suite back to baseline: 1421 passed / 30 pre-existing failures.
Diffstat (limited to 'Cargo.toml')
0 files changed, 0 insertions, 0 deletions