ispyisail 65299e1178 Let a script define and select auto-numbering ...

autoNums(kind)                 list contexts and their formulas
  addAutoNum(kind, name, parts)  define one; parts are "type[:value[:increase]]"
  removeAutoNum(kind, name)
  useConductorAutoNum(folio, n)  new conductors on a folio take it

Kinds are conductor, element and folio. Part types are the ones the
auto-numbering dialog offers; anything NumerotationContext rejects, an
unknown kind, a non-numeric increase or a missing context is refused
with a reason rather than dropped.

Defining and removing a context is not undoable, because the
application does it through direct project calls; only the counter
advance is on the undo stack. useConductorAutoNum sets both the folio's
name and the project's current name, because the numbering code reads
the context by one and writes the advanced counter back under the other.

Verified: a "W" + unit context selected on a folio, two conductors
wired, W1 and W2 in the saved file, and the context survives reload.
Depends on the preceding ConductorCreator fix for the database to agree
with the drawing.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

2026-09-22 21:56:30 +12:00

..

qetscriptapi.cpp

Let a script define and select auto-numbering

2026-09-22 21:56:30 +12:00

qetscriptapi.h

Let a script define and select auto-numbering

2026-09-22 21:56:30 +12:00

qetscripting.cpp

Fix scripting review findings: import, save, backups, timeout

2026-09-16 22:28:06 +12:00

qetscripting.h

Add geometry editing, undo integration, and navigation to scripting

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