workshopsoft/ludic
2
0
Fork 0
Code Issues Pull requests Projects Releases 26 Packages Wiki Activity Actions

ludic.ui: an override's path is compared normalised, and an absolute path matches the relative one it ends with - a lab build registers its components as lab/../src/ui/..., so the studio's src/ui/... (or absolute) path matched nothing and the override changed nothing; nothing is normalised while no override stands; examples/library/ui_override_up registers under a .. path as the lab does

Browse source 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Orkun ÇAKILKAYA 2026-09-29 23:00:12 +03:00
parent b3076597e5
commit 82c652ca31
6 changed files with 93 additions and 18 deletions
Download patch file Download diff file Expand all files Collapse all files

4
changes/ui-override.md
View file

@ -6,3 +6,7 @@ and an importer reads the new text. `ui_override_clear(path)` (or `""` for every
and `ui_overridden(path)` says whether one stands. A developer build's disk polling leaves an overridden
component alone. For a studio editing a running game's interface (devlink's `ui_override`); a game that
overrides nothing pays a length check per file read.
The override's path is compared normalised, and an absolute path matches the relative one it ends with: a
game's lab build registers its components as `lab/../src/ui/...`, and a studio's `src/ui/...` (or its
absolute path) named nothing, so an override answered ok and changed nothing.