3 Commits

Include renames

Author	SHA1	Message	Date
adminandClaude Opus 5	41772e53f7	Variables assets can keep their values from one run to the next (#166) ... A game needs a high score or an unlocked level to survive the end of a run. As agreed in the issue there are no save or load nodes. A Variables asset gets a switch instead, and the existing Variables nodes read and write the values as before. - A "Persistent" checkbox in the Variables inspector. Toggling it is one undo step, and absent means not persistent. - The behavior system loads the saved values at start and writes them after every frame that changed one, so a closed tab loses nothing. - Values live in localStorage per project, not in the project file. Another browser or person starts fresh. - Play and "Run in editor" save apart, so trying a behavior in the editor leaves the Play save alone. - Saved values are read through the current declaration. A removed variable drops out, a new one starts from its default, and a changed kind is converted. - "Clear saved values" in the inspector clears this asset in both areas. The main menu gets "Clear saved data" for the whole project. Clearing takes effect from the next run on. Decisions: - The switch covers the whole asset, not single variables. Mixing both means two assets. - A changed default in the inspector shows only after the save is cleared. That is what persistent means. Findings: - The first e2e run died at "debug hook present" right after a Vulkan error from Chrome. The second run passed, so it was a GPU flake at start-up. Tests: - ./check.sh: 140 files, 2070 tests, exit 0 (before 138 / 2055). - 15 new unit tests in tests/core/saved-values.test.ts and tests/editor/saves.test.ts. - GM_STEPS=32,46 fresh: ALL PASSED, 24 checks. Six new checks in module 32 go through the UI. Module 46 knows the new menu entry. - Counter-checks both fail as expected. Loading switched off: 2 unit tests and 2 e2e checks fail. Editor run writing into the Play area: 1 e2e check fails. - Check total 1278 (1272 measured by CI at bbbf341, plus 6). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-22 10:23:57 +02:00
adminandClaude Opus 5	da35f10d1a	The undo and redo arrows read as arrows now, and the run buttons sit on the middle of the window: the first pair was a three-quarter circle with a triangle at the end of the arc, which at 16 units puts the head exactly where the arc already is - the two melt into one another and the icon reads as a comma, which is what the screenshot showed - so both are drawn as a flat head standing free beside its tail, a triangle pointing left with a tail curving away to the right and down (redo mirrored), and they were checked in the real build, not only in an SVG renderer, because ImageMagick draws these paths a good deal more kindly than Pixi does; the play/pause pair was off centre because the row has three flexible children - the two spacers around it and the notice label, which is flexible since #177 so that the bar does not overflow at 1280 px - and each takes a third of what is left, so Toolbar.layout() now moves the pair onto the middle of the bar after super.layout(), clamped between the redo edge and the start of the notice so that a narrow window pushes the pair back instead of laying two captions on top of each other; one new e2e check in 46a measures that middle against innerWidth/2 (1148 checks), and the README gained the screenshot of the editor ... Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-20 16:51:34 +02:00
adminandClaude Opus 5	60d0146bde	The topbar is icons only: the leading Project dropdown, the Scene picker and the labelled Play/Pause buttons are gone and in their place stand five icon buttons - menu, undo, redo on the left, play and pause in the middle - while Notice, the save state, fps and the Account menu keep the right side; the Play button swaps its icon for a stop square while the project runs and Pause swaps for a second play sign while it is held (Button.setIcon()), and iconSpace() drops the gap between icon and label when a button has no label, which is what kept a 24 px icon button 3 px off its own centre; the menu carries New project, Open project..., a separator and Project settings..., where the picker (src/editor/OpenProjectDialog.ts) preselects the open project and marks it "open", opens on a double click and puts Delete on the left of Cancel and Open - it closes itself before it asks whether to delete, because two modals on top of each other would have left the question standing over a list it no longer speaks about - and the settings dialog (src/editor/ProjectSettingsDialog.ts) holds the name, the "Play starts" switch (Start scene / Active scene, a preference of this browser and so no command) and the collision layers from #152, which retires CollisionLayersDialog.ts and the "Collision layers..." entry; what Apply actually writes is the pure function settingsChanges(), so renaming and the layers are each their own undo step and each drop out when nothing differs; the Scene dropdown falls away without replacement, the active scene is switched by double clicking it in the Assets panel, which is the way that was there anyway; new module 46 runs last with 9 checks (no label left in the bar, the run buttons in edit mode, the four menu entries, the picker with the open project preselected, Cancel leaving the project standing, the settings dialog on the state of the project, renaming with undo and redo through the icon buttons) and it neither opens nor deletes a project, because that would pull the project out from under every earlier module; modules 8, 18 and 35 and the harness follow the new bar, 6 unit tests cover settingsChanges and 3 the icons (#183) ... Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-20 16:34:14 +02:00