[feature] Copy or move layers between pages #5

Closed
opened 2026-10-17 22:14:30 +00:00 by masi · 1 comment
Owner

Context: PaperCraft build of 2026-10-17, project with several pages.
Need: copy or move artboards (or any layers) from one page to another. move_nodes only reorders inside a page, and <x-paper-clone> only clones within a page.
Repro: move_nodes {nodeId:<artboard on page A>, parentId:"root", pageId:<page B>} has no such parameter; write_html with <x-paper-clone node-id="<id on page A>"/> into page B finds nothing.
Workaround: regenerate the design on the new page from a script, delete the old one, fix every reference to the old node ids.
Impact: reorganising a crowded page into pages costs a full rebuild and breaks ids referenced from specs. Suggest move_nodes with a toPageId, or a copy_nodes tool, keeping ids or returning an id map.

**Context:** PaperCraft build of 2026-10-17, project with several pages. **Need:** copy or move artboards (or any layers) from one page to another. `move_nodes` only reorders inside a page, and `<x-paper-clone>` only clones within a page. **Repro:** `move_nodes {nodeId:<artboard on page A>, parentId:"root", pageId:<page B>}` has no such parameter; `write_html` with `<x-paper-clone node-id="<id on page A>"/>` into page B finds nothing. **Workaround:** regenerate the design on the new page from a script, delete the old one, fix every reference to the old node ids. **Impact:** reorganising a crowded page into pages costs a full rebuild and breaks ids referenced from specs. Suggest `move_nodes` with a `toPageId`, or a `copy_nodes` tool, keeping ids or returning an id map.
Author
Owner

Fixed in commit 5169fe6 and released in v0.3.1.

Fixed in commit 5169fe6 and released in v0.3.1.
masi closed this issue 2026-10-17 23:04:51 +00:00
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: masi/papercraft#5