mirror of
https://github.com/qelectrotech/qelectrotech-source-mirror.git
synced 2026-09-27 20:44:13 +02:00
ispyisail
a542b911e9
qet.searchAndReplace(kind, field, pattern, replacement, useRegex, caseSensitive) finds and replaces a substring or regular expression within one text field across every folio, as a single undo step -- kind is element_info, conductor or text. Unlike a script loop over elementInfo()/setElementInfo() (or the conductor/text equivalents) doing the same thing one item at a time, each pushing its own undo entry, this wraps the whole run in one macro. This is deliberately NOT a wrapper around QET's own "Search and replace" panel (SearchAndReplaceWorker): that one is a batch overwrite-with-sentinel template built for picking items from an interactive tree, a poor fit for a script that can already say precisely which items it means. This does what the name plainly says instead -- an actual substring/regex replace within each item's current value. Found and fixed while writing the first conductor-kind test: a hub topology (several conductors sharing one terminal, e.g. a star wiring) made the conductor branch pick terminal1 unconditionally to address a Conductor object through setConductorProperty() -- for a hub member conductor, terminal1 is the shared, ambiguous hub terminal itself (findConductor() correctly refuses to address a conductor through a terminal carrying more than one), so every conductor touching that hub silently failed to update, returning a changed count of 0 with no error for a genuinely matching project. Fixed by preferring whichever of terminal1/terminal2 carries exactly that one conductor. Also caught during testing: an empty macro (a run that matches nothing) still gets pushed onto the undo stack by QUndoStack::endMacro() -- it is not silently discarded the way the earlier revision assumed -- leaving a confusing no-op "Rechercher et remplacer" undo entry. Fixed by counting matches in a dry run first and never touching the undo stack at all when that count is zero. textContent() is a new small getter alongside the existing setTextContent(), filling a gap this needed (reading an independent text's current content) that is independently useful too. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>