ispyisail 353dbd3317 Scripting: list a folio's conductors by uuid and find their ends ...

A script could name a conductor only by one of its ends, "the conductor on
terminal N of element X", which fails where two conductors meet at one
terminal and cannot follow a conductor that is re-connected.

qet.conductorUuids(folio) lists the folio's conductor uuids, in the order
qet.conductors() lists them. qet.conductorEnds(folio, uuid) returns that
conductor's two ends as "{element uuid} terminal N" -- the form
conductors() prints and the conductor calls take -- or an empty list if
the folio has no such conductor. The end formatting conductors() already
did is shared rather than copied.

Conductors of older projects have no saved uuid yet, so theirs change
from one load to the next until that is settled (discussion #1103); new
conductors keep theirs.

tst_scriptconductoruuid runs a script through --run on a fixture: every
conductor has a distinct uuid, and its ends match the conductors() line
at the same position; an unknown uuid, a malformed one and a folio that
does not exist give empty lists. It fails with the two ends swapped.

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

2026-09-28 21:07:16 +13:00

..

qetscriptapi.cpp

Scripting: list a folio's conductors by uuid and find their ends

2026-09-28 21:07:16 +13:00

qetscriptapi.h

Scripting: list a folio's conductors by uuid and find their ends

2026-09-28 21:07:16 +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