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

Docs: the macro page's conflict rules wrap at the page's width

Browse Source
This commit is contained in:
prxnvt
2026-10-25 02:49:42 -04:00
parent 65cbcdd6bd
commit 2cf5b808b3
1 changed files with 5 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/macros.md
+5 -4
View File
@@ -115,10 +115,11 @@ refused rather than read as the header.
step that writes over cells outside the inputs that held data when the run started, or deletes
sheets or objects that were there, stops the run, which rolls the workbook back (a file already
written stays). Moving such cells, as inserting or deleting rows or cells above them does,
counts as writing over them: the check compares cells by place. The rule is `onConflict` (or the macro's `output.onConflict`): `ask` (the call
fails with `confirm: …`; `overwrite: true` answers it), `fail` or `overwrite`. Shifting the
data to make room (`shiftDown`, `shiftRight`) needs to know where the macro writes before it
runs, which this version doesn't work out, so those rules stop the run as `fail` does.
counts as writing over them: the check compares cells by place. The rule is `onConflict` (or
the macro's `output.onConflict`): `ask` (the call fails with `confirm: …`; `overwrite: true`
answers it), `fail` or `overwrite`. Shifting the data to make room (`shiftDown`,
`shiftRight`) needs to know where the macro writes before it runs, which this version doesn't
work out, so those rules stop the run as `fail` does.
3. **Run.** One undo step, "Run Macro: Totals". Any error rolls the whole run back and names the
step: `Step 3.1 (cell.set): …` (paths are 1-based; `2.1` is inside a Repeat, `4.then.1` inside
an If). The message ends "Nothing was changed.", or names the files the run already wrote,