FABRIC.md item 4.4z: draw the scroll box's visible border
draw_box_border() (vt100.c) strokes four 1px edges around the 640x480 CANVAS box, reusing the same border-gray constant the REPL strip's border lines use (renamed VT100_STRIP_BORDER_GRAY -> VT100_BORDER_GRAY since it's now shared -- one pinned color decision, 4.4w, not two). Called from erase_display()'s box-scoped branch so the border survives every box clear (the initial one and any later ESC[2J), not just the first. Verified: three-arch clean QEMU boot + logs, amd64 screendump showing a full rectangle outline around the box, visually distinct from the strip below it. Punch list §25 item 4.4z complete. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Sonnet 5
parent
91742e02f4
commit
b21aa50a14
@@ -6028,7 +6028,7 @@ document and committing that amendment as its own item.*
|
||||
> **DECIDED 2026-08-12 — Ctrl+TAB.** Chosen by Captain Bob directly. 4.4v's interception
|
||||
> code intercepts this specific combination, not bare TAB.
|
||||
|
||||
- [ ] **4.4z — Draw the scroll box's visible border.** 4.4t confined REPL text to the 640×480
|
||||
- [x] **4.4z — Draw the scroll box's visible border.** 4.4t confined REPL text to the 640×480
|
||||
box's coordinate space but never stroked a visible rectangle outline on it — the box's edges
|
||||
are implicit (where text stops), not drawn. 4.4u step 6 calls for "an actual stroked
|
||||
rectangle outline." Small, separable from 4.4v/4.4r — a single `fb_fill_rect()`-based
|
||||
@@ -6039,6 +6039,18 @@ document and committing that amendment as its own item.*
|
||||
locks in (see 4.4w); three-arch QEMU boot + logs per CLAUDE.md.
|
||||
*Refs:* §27.8, 4.4t, 4.4u, 4.4w.
|
||||
|
||||
> **DONE 2026-08-12.** `draw_box_border()` (`vt100.c`) strokes four 1px edges around the box
|
||||
> using the same `VT100_BORDER_GRAY` constant the strip's border lines use (renamed from
|
||||
> `VT100_STRIP_BORDER_GRAY` since it's now shared by both — one pinned color decision,
|
||||
> 4.4w, not two). Called from `erase_display()`'s box-scoped branch (`mode==2`, TTF mode),
|
||||
> right after the box-clear fill — this covers both the initial clear at
|
||||
> `vt100_enable_ttf()` time and any later `ESC[2J`, so the border survives every box clear,
|
||||
> not just the first, per this item's own done-when. Three-arch QEMU boot + logs clean
|
||||
> (`logs/20260812-150341/amd64`, `logs/20260812-150426/aarch64`,
|
||||
> `logs/20260812-150540/riscv64`); amd64 screendump
|
||||
> (`logs/screendump-4.4z/amd64-border.png`) shows a full rectangle outline around the box,
|
||||
> visually distinct from the strip below it.
|
||||
|
||||
- [ ] **4.5 — URGENT, flagged by Captain Bob 2026-08-11: the kernel build has never used any
|
||||
compiler optimization.** **Blocking priority, set by Captain Bob 2026-08-11: no other
|
||||
punch-list item is worked until 4.5a–4.5f are done**, ahead of whatever would otherwise
|
||||
|
||||
Reference in New Issue
Block a user