From d33f40be5f20ca6c0298b70f6c83a048158da512 Mon Sep 17 00:00:00 2001 From: Sylpheed RE agent Date: Wed, 19 Aug 2026 03:13:37 +0000 Subject: [PATCH] docs/re: note that the viewer shares the compositor path Checked rather than assumed: the Bevy viewer's UI Screens browser calls the same ui_layout::compose, so the measured paint order and the ghost skip reach the window a person looks at, not just the CLI's screen render. Its element table stays in declaration order, so the per-element visibility toggles still index correctly. --- docs/re/BACKLOG.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/re/BACKLOG.md b/docs/re/BACKLOG.md index 0e68c1b5..2a6384e4 100644 --- a/docs/re/BACKLOG.md +++ b/docs/re/BACKLOG.md @@ -22,7 +22,11 @@ declaration order elsewhere. Rendering that exposed a second defect the same capture settles — `kind = 0x4` elements are motion-trail ghosts, absent at rest — and the title now composites correctly ([`captures/title-composited-measured-order.png`](captures/title-composited-measured-order.png)). -Disc-gated test, checked both ways. +Disc-gated test, checked both ways. The Bevy viewer's UI Screens browser calls +the same `ui_layout::compose`, so the fix reaches what a person actually looks at +rather than only the CLI's `screen render` — checked in `iso_loader.rs` +(`compose_screen`), which also keeps its element table in declaration order, so +the per-element visibility toggles still line up. **Still open:** deriving the order from the bundle for screens nobody has captured. It is not in the declaration entry, the placement region or the runtime