Thanks Ispyisail for the detailed trace.

New macOS build was uploaded.

Enjoy it!

Je reprends un dossier d'une installation assez importante, un point moins de 100 pages de schémas électriques, pour intégrer ce qui a été mis à jour depuis son installation.
Pour que la maintenance s'y retrouve, je veux garder la même numérotation des folios, car les repère d'élément et de fil commencent par le numéro de folio. (classique)
Seulement, la page de garde dans Qelectrotech commence à 1. La numérotation automatique des folios est donc décalé de 1 et ne correspondent plus à l'installation.

La seule parade que j'ai trouvé est de renseigner dans les propriétés du folio le numéro réel dans la propriété "Folio" de chaque page.

Y a-t-il une autre façon? Est-ce que l'on peut démarrer la variable "%id" de 0 par exemple?

Sincèrement

Alexis

I've implemented folio-level Mirror and Flip of elements over the last week, as asked for in a few old threads, here and here, and also wanted by me for a long time (for creating avionics equipment interconnect diagrams). This complements plc-user's earlier work, which added rotate/mirror/flip of graphical primitives within the Element Editor. The key difference and benefit: mirror/flip now also works at folio level, live and non-destructively, on a placed element instance — so there's no longer a need to create and maintain otherwise-identical left/right duplicate .elmt files in the symbols collection.

It's been tested very thoroughly at code level (qDebug probes through every save/reload cycle) and quite substantially while building the demo .qet and its PDF. I believe it's now ready for review, with a view to merging.

It's available on my fork:
github.com/hairykiwi/qelectrotech-sourc … irror-flip
(branch: folio-mirror-flip, built against: qt6_cmake_joshua)
I don't believe anything in it depends on Qt6, however I've only built it under Qt6.

Attachments
I'd normally attach these directly, but the forum's anti-bot still has me flagged
Here's a Dropbox link to the example .qet, its PDF output, and a technical brief (generated with Claude AI):
https://www.dropbox.com/scl/fo/yywangae … v&dl=0

Below is a mostly not-so-technical summary.

What works

Mirror and Flip on placed elements at folio level, in any combination with Rotate (90/180/etc).

Conductors stay correctly connected to their terminals through every transform — a conductor "reset" may be needed to tidy routing, but connections are preserved.

Dynamic element text (including rotated text, and grouped rotated text) survives mirror/flip and, importantly, round-trips correctly through save/reload.

One thing worth noting for backward compatibility: mirror/flip only sets a flag in the target <element> entry in the .qet. I believe older QET versions should simply ignore such flags — so files created in this branch still open in previous versions, and older files load fine here.

The attached demo project (.qet + PDF) steps through it: orientation tracking across all transform permutations, rotated and grouped-rotated dynamic text, conductors-stay-connected, non-dynamic text handling, and a basic industrial-schematic example built from the current QET symbols collection.

Two minor remaining niggles

1. After rotation, an element containing grouped rotated text will initially have that text rendered on screen as overlapping lines (see the screenshot in the Attachments). Following a save/reload cycle the layout self-corrects and stays correct. This is a separate issue from the fixed save-corruption bug (more on that below). I suspect grouped-rotated text inside an additionally rotated (and/or mirrored/flipped) element will arise so infrequently that few people will ever notice it. That said, it's on my list of tracked issues, saved for some rainy day.
2. The mirror/flip feature really wants any element text to be the dynamic text type. Static / unformatted simple text will mirror/flip as a graphic (i.e. it reverses), which is correct behaviour but usually not what you want for a label. Section 3 of the demo highlights this.

The big bug — fixed!

I doubt I could have created this feature without AI coding assistance, but the really substantial issue I leveraged Claude AI + Claude Code for was a save/reload corruption: grouped rotated dynamic text was being serialised through a "visual-preserving detach" — a routine meant for genuinely ungrouping text, which preserves its on-screen position as it detaches. On a mirrored element that routine baked the element's mirror into the child text coordinates, so on reload the mirror got applied twice and the text drifted by one group-width. That's fixed (in commit 05bcba506): now, each grouped child's geometry is serialised directly, in one frame, with no reflection baked in — the mirror stays a live flag, recomputed on load, never stored in coordinates. The mechanism and verification matrix are written up in the attached PDF for anyone who wants the detail.

A couple of related feature ideas

While testing mirror/flip (+ rotate), I found it very easy to lose track of an element's original orientation. That could matter a lot for industrial symbols that either should not, or must not, be mirrored or flipped. So I think these are worth implementing before too long, for convenience and preserving user sanity

1. A non-destructive transform reset — clear all Rotate/Mirror/Flip on an element back to its original on-disk orientation while keeping any text the user has added.
2. Mirror/Flip during placement, the way Rotate already works while inserting. The non-destructive reset above should work during placement too.

One housekeeping note: my branch carries a small local main.cpp change (an app-name tweak for my own build) that should be ignored/reverted before merge — it's not part of the feature.

I'm happy to walk through any of it, rebase as needed, and split into smaller commits if that helps review.

hairy_kiwi

EDIT: Update on Grouped-rotated text
Since posting, I've been testing the trickier combinations more closely and want to flag two rough edges, both confined to grouped rotated text and both to the live, unsaved on-screen render — the saved file is always correct, and once you save and reopen, the element displays and prints/exports correctly. Persisted data is never affected.

Grouped rotated text can momentarily overlap on screen while rotating an element (at odd 90° steps from the last-saved orientation). This looks like it may be independent of mirror/flip — i.e. possibly a pre-existing rotation rendering issue — and I'm investigating it separately.
Mirror/flip of grouped rotated text on an element that's also rotated (90°/270°) isn't yet transforming correctly in the live view. At 0° it's fine; the rotated combination needs more work, likely the same fix I applied to ungrouped rotated text extended to the grouped path.

Both are low-impact in practice (grouped rotated text is uncommon, the rotated+mirror/flip combination more so), and the feature is fully correct for the common cases. I'll post another update here as and when I have time. Details in the technical brief.

Voilà, le  fichier est là!

Guten Tag,
Im ZIP-Archiv finden Sie eine Sammlung von Elementen und Beispielen von Schaltplänen, die ich 2014 erstellt habe und die auch 2026 noch mit QelectroTech verwendet werden können. Das ist ganz im Sinne von QelectroTech, einer Open-Source-Software, die die Nachhaltigkeit der Projekte gewährleistet.
Sie finden auch Zeichnungenvorlagen mit einer Schrifteld gemäß ISO 7200 und eine Beschreibung der Felder dieser Kartusche.

Hello,
In the ZIP archive, you will find a collection of elements and schematic examples that I created in 2014 and that can still be used with QelectroTech in 2026. This is a credit to QelectroTech, an open source software that ensures the sustainability of projects.
You will also find model drawings with a title block according to ISO 7200 and a description of the fields in this title block.

Autre chose, il y a une nouvelle notion de "modèle" ou de "macro". C'est quoi ?

Merci.
Cordialement.

I am running Linux Mint. A few moths ago I have downloaded the source code of qet 0.100 compiled and installed it, modified part of the source code to fix some issues, uninstalled the old installation and re-installed it.

Yesterday, I noticed that files of other custom software installed under /usr/local/share/icons and /usr/local/man were missing. Only qet files were left in these directory trees.

So, I had a look at the Makefile of qet 0.100 and found the following section in Makefile.Release:

uninstall_icons: FORCE
        -$(DEL_FILE) -r $(INSTALL_ROOT)/usr/local/share/icons/hicolor/256x256
        -$(DEL_FILE) -r $(INSTALL_ROOT)/usr/local/share/icons/hicolor/128x128
        -$(DEL_FILE) -r $(INSTALL_ROOT)/usr/local/share/icons/hicolor/64x64
        -$(DEL_FILE) -r $(INSTALL_ROOT)/usr/local/share/icons/hicolor/48x48
        -$(DEL_FILE) -r $(INSTALL_ROOT)/usr/local/share/icons/hicolor/32x32
        -$(DEL_FILE) -r $(INSTALL_ROOT)/usr/local/share/icons/hicolor/22x22
        -$(DEL_FILE) -r $(INSTALL_ROOT)/usr/local/share/icons/hicolor/16x16
        -$(DEL_DIR) $(INSTALL_ROOT)/usr/local/share/icons/hicolor/

uninstall_man: FORCE
        -$(DEL_FILE) -r $(INSTALL_ROOT)/usr/local/man/ru
        -$(DEL_FILE) -r $(INSTALL_ROOT)/usr/local/man/pt
        -$(DEL_FILE) -r $(INSTALL_ROOT)/usr/local/man/pl
        -$(DEL_FILE) -r $(INSTALL_ROOT)/usr/local/man/nl
        -$(DEL_FILE) -r $(INSTALL_ROOT)/usr/local/man/man1
        -$(DEL_FILE) -r $(INSTALL_ROOT)/usr/local/man/it
        -$(DEL_FILE) -r $(INSTALL_ROOT)/usr/local/man/fr.UTF-8
        -$(DEL_FILE) -r $(INSTALL_ROOT)/usr/local/man/fr.ISO8859-1
        -$(DEL_FILE) -r $(INSTALL_ROOT)/usr/local/man/fr
        -$(DEL_FILE) -r $(INSTALL_ROOT)/usr/local/man/es
        -$(DEL_FILE) -r $(INSTALL_ROOT)/usr/local/man/el
        -$(DEL_FILE) -r $(INSTALL_ROOT)/usr/local/man/cs
        -$(DEL_FILE) -r $(INSTALL_ROOT)/usr/local/man/ca
        -$(DEL_FILE) -r $(INSTALL_ROOT)/usr/local/man/be
        -$(DEL_DIR) $(INSTALL_ROOT)/usr/local/man/ 

These lines suggest that per "make uninstall" entire folders are removed, that may hold files from other software, rather than removing only qet files.

Therefore, I recommend to please correct the uninstall procedure carried out per Makefiles so that only qet files are removed.

Regards
Tom

I had to cut half of my post and could not attach an image because of this error:
The BB software is giving me error message saying "Warning! The following errors must be corrected before your message can be posted: Sorry, but we think you are bot. You can not post message on this forum."
How do I prove that I am not a bot?

UPDATE: Thanks to guidance from Laurent Trinques, I was able to upload the image. I hope to receive advice soon.

Ich habe hier exemplarisch ein HMI, welches auf einer Seite im Schaltschrank gezeichnet ist. Das HMI ist aber tatsächlich extern in einem Pult verbaut. Somit wird dies als extern durch eine gestrichelte Linie gekennzeichnet. Nun zum Problem, beim BMK für das HMI wird der Ort (%LM) von der Schaltplanseite übernommen, nicht der Ort vom Element selbst. Gibt es hierzu eine andere Bezeichnung in der BMK-Formel und den Ort, Anlage,... des Elementes selbst in das BMK zu übernehmen anstatt der Folien-Eigenschaften? Gibt es Einstellungen im in den Projekteigenschaften oder den Einstellungen von QElectroTech selbst? Ich finde hierzu nichts.
Natürlich kann das Panel auch auf eine eigene Folie gezeichnet werden, welche dann +EXT als Ortskennzeichen hat. Aber es ist gängige Praxis dies auch auf anderen Folien zu zeichnen mit der gestrichelten Umrandung als Kennzeichnung.
Wenn in den Element-Eigenschaften keine Anlage/Ort angegeben wird, so wird dies auch nicht im Betriebsmittelverzeichnis angegeben.

I have copied an existing file for another project. When I export the BOM to a sqlite database I still
in the database which are not used. They are not in the visible project but still in th database.
Purging or clenaing up the project doen`t help. They are still in.

The strange thing is that the same query in the software doesn`t show these elements.
What is the reason for this and how can I get rid of the unused also in the sqlite DB?

Thank you.

Chris