ispyisail b99f5551d2 Scripting: look up a folio by its uuid ...

Every scripting call names a folio by its index, and the index shifts when
a folio is added, removed or moved: a script that removes folio 0 and then
edits "folio 2" edits the wrong one. Texts, shapes, pictures, tables and
symbol text fields already have a uuid lookup for the same reason; folios
had none.

- qet.folioUuid(index): the folio's uuid, or "".
- qet.folioIndex(uuid): the folio's current index, or -1.

A folio saved without a uuid (132 of the 133 in the shipped examples) is
given one on load, derived from the file, so it is the same on every load
and is written on the next save. No two folios share one: a clash is
renewed on load.

Tests in misc/qet-mcp's integration suite, which drives these through
--run: a folio followed across the removal of the one before it, on a file
saved without folio uuids, and a new folio's uuid found in the saved file.
Both fail against a build without this change.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-09-28 23:56:08 +13:00

..

qetscriptapi.cpp

Scripting: look up a folio by its uuid

2026-09-28 23:56:08 +13:00

qetscriptapi.h

Scripting: look up a folio by its uuid

2026-09-28 23:56:08 +13:00

qetscripting.cpp

Scripting is off until asked for, and says how to turn it on

2026-09-23 04:06:33 +12:00

qetscripting.h

Add geometry editing, undo integration, and navigation to scripting

2026-09-16 20:20:58 +12:00