fix(client): keep nutrient readouts on stable single-line rows

This commit is contained in:
dingo
2026-10-26 17:30:47 -04:00
parent 82d21e65b2
commit 7ca5f74f03
6 changed files with 136 additions and 16 deletions
@@ -52,6 +52,13 @@ a scrollable details area. Changing nutrient values, growth warnings, pending
results, region-edge notices and stale observations cannot resize or re-anchor
these panels. The responsive compact layout keeps the dock and map within the viewport.
Resource-table rows also have stable single-line geometry: names and formatted
quantities never inherit prose wrapping. The amount column reserves the widest
supported energy/mass readout at the current font/scale, including the full u64
range, independently of live values. A growth-limiting nutrient shows `*` in its
existing dot slot, with the same bar outline; the marker never lengthens an amount.
This prevents transitions such as `714 fg` to `1.54 pg` from shifting later rows.
Nearby is a camera-centred observation map with a fixed six-millimetre radius.
It reads the received food and organism views only, including observations
outside the viewport. Empty space means unknown, not confirmed empty. Rings
+52
View File
@@ -10293,3 +10293,55 @@ application restarts. Hardware DPI, accessibility, touch interaction and motion
comfort still need interactive review. No deployment, live session, World0 change,
reset or prune occurred. The required pre-push session-window refresh is desired
Git configuration only.
## 2026-10-26 - String-length stability inside nutrient tables
Reviewed the supplied Recording 2026-10-26 171124.mp4 locally (420x428, 5.83 s).
The outer Vitals card was already fixed; its carbon amount changed from
714 fg * to 1.54 pg *, wrapping the marker and shifting later nutrient rows.
The prior outer-geometry regression did not check those inner row baselines.
Changes: quantity/name cells explicitly disable prose wrapping; a font/scale-based
fixed amount-column width covers the largest supported energy and mass readouts.
The growth-limiting * occupies the existing nutrient-dot slot, with unchanged
bar outline and explanatory legend. No number formatting, simulation rule,
checkpoint, protocol, dependency or public API changed. The shared table also
serves mutation cost readouts.
Executed:
- First added the native table-geometry regression without the fix. It failed
at the baseline/height assertion on the old renderer, reproducing the recording.
- GCC 14.2 Release/NDEBUG, build/playtest-release: rebuilt evo-client and native
panel tests. Focused panel CTest passed; the final executable also passed with
review screenshots under SDL_VIDEO_DRIVER=dummy and SDL_RENDER_DRIVER=software.
- Regression spans 714, 999, 1000, 1540, 9999, 10000 and higher unit boundaries,
zero and UINT64_MAX. It checks unchanged last-row baseline, total table height,
amount-column width and zero horizontal overflow. Viewports are 640x480,
960x640, 1280x800 and 1600x1008; the latter exercises the recording's 1.4 scale.
Existing dragging, anchoring, Bud, mutation and death/restart paths still run.
- MSVC 19.44 client preset check: build succeeded and client CTests passed 10/10.
TMP/TEMP used ignored build/playtest-windows-tmp.
- Clang 19 analysis-preset build/playtest-analysis: production client and panel
regression built with clang-tidy and warnings as errors.
- Clang 19 ASan+UBSan build/client-asan: focused native panel CTest passed 1/1.
- Changed C++ files passed clang-format 19 dry-run. The full format-check initially
found an existing wrapping violation in cellular_revamp.cpp; normalized those
lines only, verified identical non-whitespace text, and the full gate passed.
git diff --check passed. No server behavior changed by that formatting correction.
- Visually reviewed generated Vitals crops for 714 fg, 1.54 pg and UINT64_MAX at
1.4 scale in ignored build/string-bounce-review/fixed/stock-comparison.png.
All four rows stay aligned and the full formatted maximum remains visible.
Video decoding used the existing ignored review-tool FFmpeg, not a new runtime
or repository dependency.
Limits: local software-renderer fixtures do not replace interactive hardware DPI
and accessibility review. No deployment, World0 change, reset or pruning was
performed. Existing unrelated drafts and untracked files were preserved; the
required pre-push session-window update is desired Git configuration only.
Publication limit: the scoped commit was created locally, but the configured
Gitea remote returned HTTP 500 during push. Two bounded read-only remote checks,
including a delayed HTTP/1.1 check, returned the same server error. Publication
remains pending remote recovery. No force push, credential-store change, server
operation or deployment was attempted.