fabi/Syplheed-Reborn
Archived
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs/re: note that the viewer shares the compositor path

Browse Source 
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.
This commit is contained in:
Sylpheed RE agent
2026-08-19 03:13:37 +00:00
parent 8c08c211a3
commit 343864cc2f
1 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/re/BACKLOG.md
View File

@@ -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 — capture settles — `kind = 0x4` elements are motion-trail ghosts, absent at rest —
and the title now composites correctly and the title now composites correctly
([`captures/title-composited-measured-order.png`](captures/title-composited-measured-order.png)). ([`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 **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 captured. It is not in the declaration entry, the placement region or the runtime