Start: no flash of default sizes before the saved display settings apply #122

Open
opened 2026-10-29 16:50:29 +00:00 by claude-bot · 0 comments
Collaborator

Follow-up from the #12 phone QC (owner, comment 2437): at start there is a very short flash before the saved display settings are in place. The log shows the default sizes first, then the saved ones, in the same frame (16:37:03 on build 9c6ab1825). It is polish for after 0.1.

Owner's options:

  • Show the window only once every setting is loaded, so the Ubuntu Touch splash screen stays up until then.
  • Or add a loading splash of our own, if one turns out to be needed.

Notes for whoever picks this up:

  • First find which property flips. Likely the Theme's text size, face and spacing bindings, which start at their defaults and then get the core's saved values.
  • Ideally the QML would read them before the first frame, for example as initial values handed to the engine from main.cpp, or by keeping the window hidden until the reader reports its settings.
  • Start-up budget (docs/07): this must not add start-up work beyond reading a few settings that are already read. State the effect on time-to-text in the PR.
  • Proof: a log line, or a first-frame shot, showing no layout pass with the default sizes when the saved ones differ.

🤖 Generated with Claude Code

Follow-up from the #12 phone QC (owner, comment 2437): at start there is a very short flash before the saved display settings are in place. The log shows the default sizes first, then the saved ones, in the same frame (16:37:03 on build 9c6ab1825). It is polish for after 0.1. **Owner's options:** - Show the window only once every setting is loaded, so the Ubuntu Touch splash screen stays up until then. - Or add a loading splash of our own, if one turns out to be needed. **Notes for whoever picks this up:** - First find which property flips. Likely the Theme's text size, face and spacing bindings, which start at their defaults and then get the core's saved values. - Ideally the QML would read them before the first frame, for example as initial values handed to the engine from `main.cpp`, or by keeping the window hidden until the reader reports its settings. - Start-up budget (docs/07): this must not add start-up work beyond reading a few settings that are already read. State the effect on time-to-text in the PR. - Proof: a log line, or a first-frame shot, showing no layout pass with the default sizes when the saved ones differ. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Sign in to join this conversation.
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
schaefera/utStudyBIble#122
No description provided.