From e7e90c19c5b22f744905b6952444be8c806ed662 Mon Sep 17 00:00:00 2001 From: datatimp <12644819+datatimp@users.noreply.github.com> Date: Tue, 17 Nov 2026 15:45:42 -0500 Subject: [PATCH] Document the refused copy of objects beside their own top-level layer --- docs/mcp.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/mcp.md b/docs/mcp.md index 0db522ba42..b3a3a786dd 100644 --- a/docs/mcp.md +++ b/docs/mcp.md @@ -5402,7 +5402,8 @@ and `layerRows`, the rows highlighted in the panel. Intertwine for the members an Intertwine group takes; an object placed beside a top-level layer goes inside it); a row never goes into itself or a row inside it, and a locked layer or group takes nothing. With `copy`, the target may be one of the rows copied: the copies go above or below it, as an Alt-drag onto a row's own row (or a - bottom layer's into the empty space under the list) places them (#8237). Dragging the + bottom layer's into the empty space under the list) places them, unless objects are copied with a top-level layer + that is the target, which would put them inside it (#8237). Dragging the selected-art square is `layer.move` with the selected objects. `node.move {id, parent?, index}` is the low-level form with the same nesting rules; unlike `layer.move`, it also moves a row into a locked layer or group. - **Buttons**: `layer.new {name?, top?, below?, …options}` (above the current layer at its level; `top` with