ispyisail 1c1f9db3eb Scripting: qet.currentFolio(), and one undo step per script run in the editor ...

A script started from the editor had no way to know which folio is on
screen, and each qet.* call was its own undo step, so a script that adds
twenty items needed twenty Ctrl+Z to take back.

qet.currentFolio() returns the folio shown in the editor; through --run,
which has no view, the first folio, or -1 when there is none.

A run from the editor is now one undo macro, named after the script. A
run that changed nothing leaves no empty entry behind. qet.undo() and
qet.redo() inside a grouped run say why they cannot work (QUndoStack
ignores them inside a macro) instead of failing silently. --run is
unchanged: one step per call, so scripts that call qet.undo() keep
working.

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

2026-10-02 08:47:27 +13:00

..

qetscriptapi.cpp

Scripting: qet.currentFolio(), and one undo step per script run in the editor

2026-10-02 08:47:27 +13:00

qetscriptapi.h

Scripting: qet.currentFolio(), and one undo step per script run in the editor

2026-10-02 08:47:27 +13:00

qetscripting.cpp

Scripting: qet.currentFolio(), and one undo step per script run in the editor

2026-10-02 08:47:27 +13:00

qetscripting.h

Scripting: qet.currentFolio(), and one undo step per script run in the editor

2026-10-02 08:47:27 +13:00