ispyisail 528d33792d Say what order a terminal index actually follows ...

The comment on elementTerminals() said the order of Element::terminals()
"also comes from the definition", which reads as file order and is
wrong. Element::parseTerminal() re-sorts the list on every insertion, top
to bottom then left to right on each terminal's local position, so index 0
is the topmost terminal whatever order the .elmt lists them in.

bobine_ka_a_remanence.elmt writes A2 (y=20) before A1 (y=-20) and index 0
is A1. Measured by placing 400 shipped elements and reading the real order
back: a top-to-bottom, left-to-right prediction matched all 400, while
file order matched only the 100 where the two happen to coincide. Of the
837 shipped elements with distinct named terminals, 619 list them in a
different order than QElectroTech indexes them.

Comment only. Two terminals at one point tie and the sort is not stable;
the comment says so.

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

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

..

qetscriptapi.cpp

Say what order a terminal index actually follows

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

qetscriptapi.h

Say what order a terminal index actually follows

2026-09-22 21:56:31 +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