7 Commits

Include renames

Author	SHA1	Message	Date
adminandClaude Opus 5.5	2da07599d8	Let Get position give only the local x and y ... Get world position now covers the world coordinates. Two nodes that both offer world x and y made it unclear which one to take. No project uses the world outputs of Get position any more. - Get position drops its world x and world y outputs and its description points to Get world position. - Old snapshots with edges on those outputs still load. The edges hang on ghost ports and the node warns about them. - The unit tests in hierarchy and raycast and the graphs in e2e 43 use Get world position where they read the world coordinates. Tests: - node-catalog, hierarchy, raycast: 3 files, 417 tests, all green - e2e 43 on melektaus-atx: ALL PASSED, 17 checks Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-04 19:13:58 +02:00
adminandClaude Opus 5.5	b45bbcc976	Hold in tests that a graph edit reaches a running behavior (#216) ... The issue said a behavior that runs in the editor keeps the graph it started with, until it is switched off and on. Measured before building anything, that is no longer so. An edit runs from the next frame on. Since when, was not found out. - No code changes. A command raises the project event, EditorRun refreshes, and syncFromModel of the behavior system empties the graph cache. - Decided in the issue: the instance carries on and is not started over. Its variables and timers stand, and On start does not fire again. A restart would write what On start writes or spawns into the saved scene with every edit. - Starting over stays what it was: Run in editor off and on, or Play. - Module 43 of the e2e no longer switches the behavior off and on before it measures the changed layers of a ray cast. Tests: - Gate on melektaus-atx for this change alone: 212 files, 3264 tests (3260 + 4), exit 0. The gate right before this commit ran on the tree of this and the next commit together: 213 files, 3278 tests, exit 0. - e2e 18,20,43 on melektaus-atx: 57 checks, all pass. The check in 43 is the old one, it now holds without the workaround. - Four unit tests in editor-run.test.ts: a changed node setting, a node wired in and one cut off, a flow hung on On start that does not fire until the switch goes off and on, and an undo. - One counter-probe: without the emptied cache the wiring test fails. The setting test does not, settings change in place. - No full run and no smokes. The sum of e2e checks stays 1676. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-02 17:59:19 +02:00
adminandClaude Opus 5.5	0e8585665a	Load the 500 weight and draw missing glyphs as SVG icons (#214) ... The theme asks for Source Sans 3 at weight 500, but fonts.ts only loaded 400, 600 and 700. The browser synthesised the 500 text. The issue comment also asked for the symbols the font lacks to become SVG icons. A scan of src/ against the font's cmap found 20 such characters in 30 places. - fonts.ts loads source-sans-3-latin-500-normal.woff2 as well. - Menus draw their ticks and the "current" dot as icons. The dot is a new MenuItem.current field and no longer part of the label text. - Inspector action buttons (reset, apply, fit width/height) are icons. The menu arrow behind them is the drawn Dropdown chevron. - Kind marks come from a table in markIcons.ts. Picture kinds use an icon, # and Aa stay text because the font has them. - Scene marks in the asset panel, sound play/stop and the transition arrows are icons too. - Apply is an icon although the font has the arrow. It sits next to the reset icon and would look different as a glyph. - A new Icon widget draws on redraw like Button, so Node tests need no DOMParser. - Tests find icons through the SVG id. The new hook __gm.locateIcons(id) and the harness helpers findIcon/clickIcon replace locate() on the old characters. Findings: - Weight 700 is loaded but the theme never uses it. Left as is. - The old scene-mark check in module 35 accepted any play glyph on screen. It now checks the mark on the start scene's row. - Module 44 needs the textures from module 37 and fails without it. Tests: - ./check.sh: 145 files, 2187 tests, exit 0 (before 144 / 2143). - New tests/ui/fonts.test.ts: every theme weight is loaded, and every character in src/ exists in every shipped face. The cmap reader matches fontTools (231 characters). - Icon tests cover the 19 new files. Each kind mark is either an icon or text, never both. - e2e 1-16,22,30,34,35,43,44: 586 green, 0 FAIL, then 44 stopped for lack of module 37. e2e 1-16,37,44,47,48: 618 green. e2e 1-14 on the final build: 454 green. - Two new e2e checks: loaded weights in 14, a reset icon pixel in 04. - Counter-probes all fail as expected: 500 removed, a play glyph put back, the struct icon removed (one unit test each). In the browser, 500 removed and reset icon hidden fail exactly the two new checks. - Editor-suite check sum 1312 (1310 measured by CI at 056a622, +2). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-09-23 08:13:22 +02:00
adminandClaude Opus 5	ffdf0a8ddb	The new node "Raycast all" answers with every collider along the ray instead of only the nearest one: it carries the same inputs and settings as Raycast (Ignore owner, Hit triggers, Layers from #158) plus "max hits" where 0 means all, and it hands back parallel lists sorted by distance - objects, colliders, points x/y, normals x/y, distances - next to count, so index i of every list speaks about the same hit; a collider counts once no matter how many convex parts its shape is built from, while a tilemap counts per cell it is hit in, and the filter sits in Solids.raycastAll like the one of #158, the one path the editor run and Play both take, so all 12 new unit tests run through describe.each against both systems; the node needed the value system to learn something it could not do - a graph list carried numbers, text, booleans and bundles but no object handles, asList turned an object into its name, so objects/colliders would have been lists of names, which loses the object when two carry the same name, and collider children usually do; Value now knows a travelling list that may hold handles and "Item at" gives such an item out as an object, ready for Destroy, Apply force or Name of, while the single door into a stored file - writeTyped/asTypeOf - runs the list through the new storedList() so every object becomes its name again and nothing living reaches a project file, which is its own unit test over JSON.stringify; three list nodes follow the handles: "Index of" compares objects by identity because a name is not the object of that name, "Set item" and "Fill" write an object as an object, and "Join text" prints the names instead of the innards; this decision was mine to make because the question ran into the MCP timeout - the alternative was a list of names plus "Object by name", which is the smaller change but lossy; 4 new e2e checks in the new block 43e (shield and floor in one go reading 2 and "145, 280", the second object answering to its name, which only a real object in a list can do, "max hits" 1 stopping at the nearest, and the node showing the row) and 18 new unit tests, 12 in raycast.test.ts, 4 on the value system and 2 in the node catalog; two counter-checks hold: not counting tilemap cells one by one drops 2 unit tests, and answering with the nearest hit only drops module 43 with 2 FAILs; one finding on the way - the node read "maxHits" while every other input carries a spoken label, because int() took the key as its label, so it has a third parameter now, and the e2e check caught that, no unit test did (#157) ... Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-20 18:54:12 +02:00
adminandClaude Opus 5	0fdde6cb1e	The Raycast node filters by collision layers: the node gained a "Layers" setting, a tickbox per collision layer of the project - the same field kind the collider uses for "Collides with" - and the ray only hits what sits on a ticked layer, tilemaps counting as colliders; the default is every layer, and a graph without the param answers exactly as before, which is its own unit test; the check is one-sided on purpose, unlike the symmetric rule of #152: a ray is not a collider, so it never reads the collidesWith of the thing it hits - a collider that meets nothing is still seen by a ray - because who a ray may look at is the ray's business, and a unit test holds that case; the filter sits in Solids.raycast in front of the intersection test, which is the one path the editor run and Play both take, so every unit test runs through describe.each against both systems; NodeView did not know the field kinds layer/layers, so the node would have read "Layers: 65533" - it now shows the name of the layer, or "All layers"; 5 new e2e checks in the new block 43d (a shield on its own layer between the caster and the floor stops the ray, the "Layers" row on the node, the tickbox menu with the project's layers, the ray reaching 280 instead of 145 units once the shield's layer is unticked, and the mask read as a name) and 6 new unit tests, three against each system; two counter-checks hold: disarming the filter line drops 6 unit tests and the unticking check in module 43, and switching the formatting off makes the node check fail with the raw bits; two findings from measuring came out of it and stand in the wiki and the notes - __gm.rays() only measures while the Scene tab is in front, so a node selection blinds it and the block measures through a Log node on distance instead, and a running behavior instance keeps the graph it started with, so the editor run casts with the old mask until the instance is built anew (#158) ... Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-20 18:15:35 +02:00
adminandClaude Opus 5	5385d9e152	The one-way tolerance angle is a field: a one-way collider and a one-way tile gain One-way angle (0 to 90 degrees, default 45), a contact blocks when its normal is within that angle of the blocking side, without a value the limit is bit-identical to before, and the rule holds for Move, Raycast and dynamic bodies in Rapier; tiles with different angles never merge into one rectangle, the scene view draws the angle as a cone in the middle of the thick side, and the inspector shows Blocks from and One-way angle only while One-way is on, through the new schema option shownWith (#159) ... Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-19 13:13:29 +02:00
adminandClaude Opus 5	6a31f5e0ad	One-way platforms, raycast and collision stay with contact data: a collider can be one-way with a side it blocks from (turning with its object, drawn thick in the scene view) and a tile can be one-way from above, one-way cells never merge with solid tiles, a contact blocks only when its normal is within 45 degrees of the blocking side, the new node Ignore one-way lets an object drop through for a while, and it all holds for Move and for dynamic bodies in Rapier, where the decision is made before each step because the hook may not touch the engine (#155); the new Raycast node answers hit, object, collider, point, normal and distance in our own f64 geometry, the same in editor run and play, and the editor run draws each ray for 0.25 s (#153); On collision stay gains an interval with its own clock per pair, and stay and enter gain the contact point next to normal and impulse (#149); fixes that every Rapier collider of a tilemap had the shape of its last cell ... Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-19 11:36:11 +02:00