aleleba/figcraft
1
0
Fork 0
mirror of https://github.com/storytold/figcraft.git synced 2026-10-30 21:36:46 -06:00
Code Issues Packages Projects Releases Wiki Activity

M3: component properties keep their order on rename; Make slot asks for the name (#1536, #1537) (#1565)

Browse Source 
Properties were listed by name, so a rename moved one. Components now keep prop_order (the names as they were made; a rename keeps the place) and every listing follows it. Make slot opens a name field under the frame's Slot row; Enter makes the slot, Escape cancels, a taken name keeps the field open.
This commit is contained in:
BFlat
2026-10-30 04:49:00 +07:00
committed by GitHub
parent 3c1718bf86
commit 7d76b0c673
56 changed files with 589 additions and 135 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/mcp.md
+3 -1
View File
@@ -958,7 +958,9 @@ remove and reorder layers there, unlike the rest of an instance). It is a compon
`value: {layer, edited, layers}`).
- **Define** (on the main): `component.makeSlot {id (a frame inside a main component), name?,
preferred? [component or set ids]}` (the property is named after the frame by default);
preferred? [component or set ids]}` (the property is named after the frame by default; a new
property goes last, as `component.properties` lists them in the order they were made, a rename
keeping the place);
`component.editProperty {name, preferred}`; `component.removeSlot {id}` (instances lose their own
content in it). `component.addProperty {type: "slot", layer}` and `component.bindProperty {field:
"slot"}` work too (one frame per component for a slot).