fabi/Sylpheed
1
0
Fork 0
Code Issues 9 Pull Requests Actions Packages Projects Releases Wiki Activity

re: the developer splash renders -- screen 1 of 5 finally has a composite

Browse Source 
Two pages of this corpus disagreed. MISSION says the splash "is the RATC
screen, which already renders"; ui-paint-order-key.md says it "cannot be
rendered by screen render at all". Running the tool both ways settles it.

screen list --all shows all 16 GP_TITLE entries instead of 12, and the
four the default listing drops are the splash, each half shipped twice:
entries 10 and 13 are the white SQUARE ENIX publisher logo, entries 11
and 14 the GAME ARTS / SETA / studio anima developer logos. Entry 11's
seven elements are the three logos, their three _eff glows and the
palogo_eff0.prm backdrop -- exactly the composition ui-paint-order-key.md
had measured for the splash without being able to draw it.

So the "cannot be rendered" line is wrong and is corrected in place. What
is true is narrower and worth keeping: the splash is invisible to the
DEFAULT listing because is_build wants a .rat child, so anyone who does
not pass --all concludes it is missing. That goes in METHOD -- a default
filter can hide a whole screen and the corpus will record it as absent.

The payoff is for the port rather than for the RE: the first of the five
screens now has a reference composite, which it did not have. Marked
amber on one point -- there is no framebuffer capture of the splash in
this repo, so the match to the running game is by description against the
milestone-1 notes, not by pixels.
This commit is contained in:
Sylpheed RE agent
2026-08-28 20:29:33 +00:00
parent cc8d4230b6
commit 91efa66e9c
5 changed files with 58 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
docs/re/structures/ui-paint-order-key.md
View File

@@ -84,10 +84,16 @@ Verified three ways rather than by a green build:
([capture](../captures/mission-select-derived-order.png)).
**Found on the way, and worth its own line:** the developer-logo splash bundle
has no `.rat` child, so `ui_layout::is_build` rejects it and the compositor never
sees it. Its measured order is therefore inert in practice, and the splash cannot
be rendered by `screen render` at all. That is a separate gap in what counts as a
"build", not a paint-order question.
has no `.rat` child, so `ui_layout::is_build` rejects it and the **default**
`screen render` never sees it.
⚠️ **Corrected 2026-08-28:** the sentence that used to end this paragraph — "the
splash cannot be rendered by `screen render` at all" — is **wrong**. It can:
`screen render --all` widens the enumeration past `is_build` and the splash
composites fine, both halves.
[`../ui-title-build-map.md`](../ui-title-build-map.md) has the renders. What is
true is narrower: it is invisible to the *default* listing, so anyone who does not
pass `--all` will conclude it is missing.
## What the change did to the screens that were already verified (2026-08-19)