If I remember correctly, the ‘thumbnail’ type was added only for the SQL database and for the Boom table in order to count only one element in entire the project with the same label.
Not the physical representation element for nomenclature list, off course is the same element!
1 2025-11-20 12:46:45
Re: How to properly link schematic symbol to graphical one? (12 replies, posted in EN : Help, suggestions, discussions, ...)
2 2025-11-20 10:50:31
Re: How to properly link schematic symbol to graphical one? (12 replies, posted in EN : Help, suggestions, discussions, ...)
acolomb wrote:
That label is the cross-reference back to the "master" device, which can be double-clicked to jump there. It is automatically attached to the "label" dynamic text of the element. So you need to be careful where you place that text. For the master, it will extend to a list of bound slaves, with one folio reference per slave, also showing the slave's "contact type" property symbolically.
As for contributing the elements, sure you can make a pull request to include it in the standard library, if the quality / consistency is acceptable. However, this pattern of master-slave relationships between the physical and logical symbols is not common among existing library elements. If you have for example mostly circuit breakers, for which the official library symbol already defines an according element type (master / organ of protection), then it would be kind of useful. But imagine someone not wanting to link it, they could not even give your element a label (as that is not independently possible for slaves). So it would limit the utility of the whole element.
Hallo André,
If you can attach an example of a declassified project, it could help new users and perhaps give old users some ideas.
PS: There is no obligation, and I completely understand if you do not wish to disclose your plans or solutions/workarounds.
3 2025-11-20 10:42:57
Re: How to properly link schematic symbol to graphical one? (12 replies, posted in EN : Help, suggestions, discussions, ...)
Hi Vos,
you could send a pull request on https://github.com/qelectrotech/qelectr … nt-contrib
https://github.com/qelectrotech/qelectr … ting_plate directory.
Online contreib collection viewer and download.
https://download.qelectrotech.org/qet/e … index.html
4 2025-11-19 21:21:59
Re: ISO27001 compatibility (3 replies, posted in Platform-specific problems: Windows,)
QET silent Windows package:
https://www.manageengine.com/products/d … 0.90).html
Chocolate for Windows It https://community.chocolatey.org/packages/qet
https://wapt.tranquil.it/store/fr/tis-qelectrotech
What is WAPT ?
WAPT is a secure solution for installing, updating, uninstalling software, configurations, and operating systems.It manages the full software lifecycle for companies and government organizations of any size.
Tranquil IT offers ready-to-use packages to help you quickly deploy software silently, within the scope of your subscription.
5 2025-11-19 20:17:37
Re: ISO27001 compatibility (3 replies, posted in Platform-specific problems: Windows,)
Hello Arkadiusz,
I post here what I have already replied to you by email on this subject!
Le mercredi 30 juillet 2025 12:44:05 heure d’été d’Europe centrale, vous avez
écrit :
> Good Afternoon Mr. Laurent,
>
> I would like to try your software, I know that is very useful and effective.
> I cannot install QElectrotech on my company machine without IT acceptance.
> That's why I would like to ask you about security certifications such as
> ISO27001, SOC2 Type2, or Vulnerability assessment report, Pentest report,
> etc. Without any of this, IT will not let me use your software. I know that
> there is a non-exe version, but still , I want to be "legal". Could you
> share any documents that will be evidence for IT team that your software is
> safe ? Thank you in advance,
>
>
> Pozdrawiam / Best Regards..............
............Hello Arkadiusz,
Nowadays, QET is not only used by many individuals, teachers and students but also by
professional electricians and a lot of many companies all over the world.QET is also provided on official Debian, Ubuntu, Fedora, Redhat entreprise RHEL etc repository.
My package for Windows is cross-compiled with MXE :
https://mxe.cc/
with Digikam script on my Debian
https://invent.kde.org/graphics/digikam … c0fa56a948
https://github.com/qelectrotech/qelectr … Windows.shhttps://qelectrotech.org/forum/viewtopic.php?id=1432
https://qelectrotech.org/forum/viewtopi … 976#p13976
Tip: don't try 0.90 but 0.100-dev!
Best regards,
Laurent
Btw, macOS package was submitted to Apple server:
macOS Apple Silicon arm64, signed and notarized.
Overview
Notarization gives users more confidence that the Developer ID-signed software
you distribute has been checked by Apple for malicious components.
Notarization is not App Review. The Apple notary service is an automated
system that scans your software for malicious content, checks for code-signing
issues, and returns the results to you quickly. If there are no issues, the
notary service generates a ticket for you to staple to your software; the
notary service also publishes that ticket online where Gatekeeper can find it.When the user first installs or runs your software, the presence of a ticket
(either online or attached to the executable) tells Gatekeeper that Apple
notarized the software. Gatekeeper then places descriptive information in the
initial launch dialog to help the user make an informed choice about whether
to launch the app.QET est maintenant disponible sur le MDM IDF (ile de france PARIS)
https://iledefrance-unowhy.com/?s=qelectrotech
https://qelectrotech.org/forum/viewtopi … 741#p16741
6 2025-11-17 17:27:08
Re: download of appimage failed (2 replies, posted in DE : Hilfe, Vorschläge, Unterhaltungen...)
It works without any problems here.
You could try with other utils ."You are not on Windows."... Also try wget or curl..
wget https://download.qelectrotech.org/qet/builds/AppImage/0.100.0/X86_64/QElectroTech_0.100.0-r8536-x86_64.AppImage7 2025-11-16 09:44:31
Re: How to properly link schematic symbol to graphical one? (12 replies, posted in EN : Help, suggestions, discussions, ...)
Another workaround :
https://qelectrotech.org/forum/viewtopi … 475#p16475
8 2025-11-16 07:21:58
Re: How to properly link schematic symbol to graphical one? (12 replies, posted in EN : Help, suggestions, discussions, ...)
1) use list contact view and not cross for all Xref .
2) For graphical elements change the property thumbnail to slave and select "other"
9 2025-11-16 07:07:07
Re: How to properly link schematic symbol to graphical one? (12 replies, posted in EN : Help, suggestions, discussions, ...)
Hi,
don't use QET 0.90 but 0100-dev!
See this topic for other link for master.
https://qelectrotech.org/forum/viewtopic.php?id=2264
10 2025-11-15 19:07:35
Re: Nouveautés de la version de développement 0.9 (232 replies, posted in News)
By the way, after several research, I downgraded the docutils packages in my Debian Sid, which new docutils packages version was breaking my Python Sphinx documentation needed to compile the Extra Cmake Modules. Like
File "/usr/lib/python3/dist-packages/sphinx/registry.py", line 544, in load_extension
raise ExtensionError(
__('Could not import extension %s') % extname, err
) from err
sphinx.errors.ExtensionError: Could not import extension ecm (exception: No module named 'docutils.....
Thanks Freexian team to report it: https://www.freexian.com/blog/debian-co … s-10-2025/
Now I have updated my MXE cross-compilation toolchain to last Qt 5.15.18 Framework and upgrade GCC to version:14.3.0, KF5 libs no changes, for the Windows .exe cross-compilation package.
https://github.com/mxe/mxe/commits/master/
11 2025-11-14 11:34:01
Re: Resizing an object. (3 replies, posted in EN : Help, suggestions, discussions, ...)
Hello
I draw the walls of the house (on this subject, if anyone knows where to find a library for doors and windows), but when I import a socket from the QET collection, it appears too large in the drawing space.
see: https://qelectrotech.org/forum/viewtopi … 367#p10367
Columns and rows isn't for printer paper but for scaling element view in your diagrams.
12 2025-11-14 02:46:23
Re: Nouveautés de la version de développement 0.9 (232 replies, posted in News)
Hi Carl,
this has only been reported here on the forum and on Github issues; there doesn't seem to be any entry in Mantis.
https://qelectrotech.org/forum/viewtopi … 089#p21089
Emil have writted a new documentation for compile it under Windows with Qt6.9 if some one can try?
https://github.com/EmilOsvoll/qelectrot … d_Guide.md
As indicated by plc-user, the master and qt6-cmake branches have diverged significantly. Merging the master branch into the qt6-cmake branch causes many conflicts that must be resolved manually. I tried, but I got confused... my knowledge of GIT is limited.
plc-user wrote:
- I don't know a schedule for the switch to QT6 and am very curious myself to see how the two GitHub branches will come together, given how many changes have been made to both branches in the meantime...
On Debian sid
sudo apt install qt6-tools-dev qt6-svg-dev pkg-configscorpio810 wrote:
git clone --recursive https://github.com/qelectrotech/qelectrotech-source-mirror.git cd qelectrotech-source-mirror/ git switch qt6-cmakecomment line 137 of /sources/machine_info.cpp to compile.
mkdir build && cd build cmake .. -G Ninja -DBUILD_WITH_QT6=ON time ninja -j48Ignored 95 untranslated source text(s)
[318/478] Building CXX object CMakeFiles/qelectrotech.dir/sources/editor/UndoCommand/openelmtcommand.cpp.o
/media/backup6/qelectrotech-source-mirror/sources/editor/UndoCommand/openelmtcommand.cpp: In member function ‘virtual void OpenElmtCommand::redo()’:
/media/backup6/qelectrotech-source-mirror/sources/editor/UndoCommand/openelmtcommand.cpp:66:102: note: ‘#pragma message: @TODO uncommante slot_select when fixed, see itemChange function for each primitive’
66 | #pragma message("@TODO uncommante slot_select when fixed, see itemChange function for each primitive")
| ^
[478/478] Linking CXX executable qelectrotechreal 0m36,019s
user 21m37,065s
sys 1m39,485sQElectroTech V 0.100.0-dev
Compilation : GCC 15.2.0
Built with Qt 6.9.2 - x86_64 - Date : Sep 28 2025 : 12:58:45
Git Revision : 411fb3c4dc54b6aaea00f034d6c5396de5daa474
Run with Qt 6.9.2 using 48 thread(s)
13 2025-11-13 16:39:41
Re: Nouveautés de la version de développement 0.9 (232 replies, posted in News)
scorpio810 wrote:
https://www.qt.io/blog/commercial-lts-q … 9-released
Wait one year...
https://www.qt.io/blog/extended-securit … s-may-2025
Houston, we have a problem!!!!!Standard support for Qt 5.15 will end after 26th of May 2025, as communicated earlier. After the support period, the release will be in EoS (End of Support) state and will only be supported through additional services, including Extended Security Maintenance for Qt 5.15, Extended Support, and Professional Services. Customers distributing applications and embedded devices using Qt 5.15 software should evaluate how to access technical support and maintenance patches which may include security fixes. Standard commercials terms still apply after End of Support.
https://github.com/qelectrotech/qelectr … issues/402
Qt5 is now declared deprecated in Gentoo
At this point in time, Linux distributions are starting to track which packages are blocking a future Qt5 cleanup. Real Qt Company OSS support stopped back in 2020, when public availability of LTS releases started to be delayed for 1 year, stable branch repository access got closed down (with 5.15 branch repository receiving any new LTS tag one year after commercial release) and only Qt6-relevant bugs are being fixed (then backported) since then. The final release happened on 2025-05-19, which means a) we will not get it until 2026-06-19, b) any bugs discovered since last May will not be fixed and c) no bugs since 2020-12-08 that haven't also been affecting Qt6 were fixed at all.
14 2025-11-13 16:19:10
Re: Update QET macOS aarch64 packaging to Qt Tool Kit 5.15.15 -> 5.15.17 (2 replies, posted in Platform-specific problems: macOS)
https://www.qt.io/blog/commercial-lts-q … 9-released
Wait one year...
https://www.qt.io/blog/extended-securit … s-may-2025
Houston, we have a problem!!!!!
Standard support for Qt 5.15 will end after 26th of May 2025, as communicated earlier. After the support period, the release will be in EoS (End of Support) state and will only be supported through additional services, including Extended Security Maintenance for Qt 5.15, Extended Support, and Professional Services. Customers distributing applications and embedded devices using Qt 5.15 software should evaluate how to access technical support and maintenance patches which may include security fixes. Standard commercials terms still apply after End of Support.
15 2025-11-13 12:47:32
Re: Probleme mit Wayland (11 replies, posted in DE : Hilfe, Vorschläge, Unterhaltungen...)
For history:
https://github.com/KDAB/KDDockWidgets/issues/10
https://qelectrotech.org/bugtracker/vie … 59891ad51d
David Edmundson added a comment - 30 Jul '25 09:11
The protocol mentioned above got merged and standardised as https://wayland.app/protocols/xdg-toplevel-drag-v1QtWayland now supports this
Dates
Created: 19 Nov '22 23:08
Updated: 30 Jul '25 09:11
Resolved: 30 Jul '25 09:11
https://bugreports.qt.io/browse/QTBUG-138339
https://bugreports.qt.io/browse/QTBUG-136011
16 2025-11-13 11:37:29
Re: Probleme mit Wayland (11 replies, posted in DE : Hilfe, Vorschläge, Unterhaltungen...)
Or if you want to work under Wayland just edit /usr/share/applications/org.qelectrotech.qelectrotech.desktop
And change
Exec=qelectrotech %FBy
Exec=env QT_QPA_PLATFORM=xcb qelectrotech %FOff course! you need to change this line in *.desktop after each QET package upgrade...
For users using Ubuntu snap see: https://github.com/qelectrotech/qelectr … issues/373
17 2025-11-13 11:09:21
Re: Probleme mit Wayland (11 replies, posted in DE : Hilfe, Vorschläge, Unterhaltungen...)
scorpio810 wrote:
I "m on Debian Sid with plasma6 with Wayland and Qt6.9.
If I need to re-stack the windows because I have moved them, I run this command to switch the compositor back to X11/xcb mode and restore my windows. After that, I can restart QET normally under Wayland.QT_QPA_PLATFORM=xcb qelectrotech
18 2025-11-13 11:08:45
Re: Probleme mit Wayland (11 replies, posted in DE : Hilfe, Vorschläge, Unterhaltungen...)
I checked an little with qt6-cmake branch of QET, is better but freezing the application..
10:05:36.676 Info: "QElectroTech V 0.100.0-dev"
10:05:36.676 Info: "Compilation : GCC 15.2.0"
10:05:36.676 Info: "Built with Qt 6.9.2 - x86_64 - Date : Nov 13 2025 : 10:03:29"
10:05:36.676 Info: "Run with Qt 6.9.2 using 48 thread(s)"
10:05:36.676 Info: "CPU : model name\t: AMD Ryzen Threadripper 3960X 24-Core Processor\n"
10:05:36.676 Info: "RAM Total : 64 GB"
10:05:36.676 Info: "RAM Available : 51 GB"
10:05:36.676 Info: "GPU : Advanced Micro Devices, Inc. [AMD/ATI] Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT] (rev df)\n"
10:05:36.676 Info: "GPU RAM : Video memory: 10240MB\n Dedicated video memory: 10240 MB\n Currently available dedicated video memory: 8796 MB\n"
10:04:11.394 Info: Elements collection reload
10:04:11.516 Info: Elements collection finished to be loaded in 0.121 seconds
10:04:24.585 Warning: This plugin supports grabbing the mouse only for popup windows (:0, )
10:04:34.573 Warning: This plugin supports grabbing the mouse only for popup windows (:0, )
10:04:34.575 Warning: This plugin supports grabbing the mouse only for popup windows (:0, )
10:04:48.238 Warning: This plugin supports grabbing the mouse only for popup windows (:0, )
10:04:48.239 Warning: This plugin supports grabbing the mouse only for popup windows (:0, )
10:05:27.458 Warning: QObject::disconnect: wildcard call disconnects from destroyed signal of AutoNumberingDockWidget::AutoNumberingDockWidget (:0, )
10:05:55.454 Warning: This plugin supports grabbing the mouse only for popup windows (:0, )
10:05:58.409 Warning: This plugin supports grabbing the mouse only for popup windows (:0, )
10:05:58.412 Warning: This plugin supports grabbing the mouse only for popup windows (:0, )
10:06:22.174 Warning: QObject::disconnect: wildcard call disconnects from destroyed signal of AutoNumberingDockWidget::AutoNumberingDockWidget (:0, )
19 2025-11-13 11:01:47
Re: Probleme mit Wayland (11 replies, posted in DE : Hilfe, Vorschläge, Unterhaltungen...)
This is a Qt 5 bug and I think is fixed on Qt 6.9 or 6.10 version?
For QET we need to wait when we compile it with Qt 6.X framework
20 2025-11-13 10:55:32
Re: Probleme mit Wayland (11 replies, posted in DE : Hilfe, Vorschläge, Unterhaltungen...)
I "m on Debian Sid with plasma6 with Wayland and Qt6.9.
If I need to re-stack the windows because I have moved them, I run this command to switch the compositor back to X11/xcb mode and restore my windows. After that, I can restart QET normally under Wayland.
QT_QPA_PLATFORM=xcb qelectrotech
21 2025-11-13 10:39:13
Re: Probleme mit Wayland (11 replies, posted in DE : Hilfe, Vorschläge, Unterhaltungen...)
Hallo Thomas,
See:
https://qelectrotech.org/bugtracker/vie … d=305#c724
https://qelectrotech.org/bugtracker/view.php?id=311
I'm think this was fixed on Qt 6.9 not on old Qt 5.15.x
Regards,
Laurent
22 2025-11-12 17:24:26
Re: Update QET macOS aarch64 packaging to Qt Tool Kit 5.15.15 -> 5.15.17 (2 replies, posted in Platform-specific problems: macOS)
FYI, I just recompiled the whole digiKam macports install (9 hours of build) need for QET packaging. new public stable release of Qt5 cross-platform framework Qt 5.15.18. Before it's was commercial LTS release.
23 2025-11-12 16:23:21
Re: Où trouver des nouvelles collections ? (1 replies, posted in FR : Aide, suggestions, discussions, ...)
Bonjour Vincent!
Quel est le besoin derrière cette numérotation des bornes de tes contacts NC?
Tu as plusieurs choix qui s'offrent à toi:
Malheureusement ces numérotations ne seront pas visibles dans la représentations des références croisées dans les contacts représentés sous leur bobines maîtres..
1) Elles sont seulement visibles sur le dessin, pour aider le câblage et le dépannage?
Dans ce cas plusieurs solutions s'offrent a toi, re dessiner le symbole pour ajouter aux choix des textes dynamique, ou des textes simples immuables, ou cliquer sur ton contact NC puis aller dans l'onglet textes et ajouter deux nouveaux textes dynamiques correspondant aux numéros de bornes.
La méthode bourrin ... ajouter deux champs textes depuis l'icone ajouter un champ texte en haut dans diagram editor !
Attention c'est juste des outils d'insertions de textes et formes simples pour délimiter un coffret, armoire, machine, ou une zone, etc!!!! et les placer aux cotés du contact, c'est rapide pour prendre des notes sur le terrain à coup de copier/coller... c'est rapide pour un premier jet, MAIS, qu'il faudra ensuite reprendre tranquillement de retour au bureau... Tout est question de temps et d'organisation..! Et de plus sur un déplacement du contact ces nouveaux textes ne suivront pas l'élément déplacés...
2) Pouvoir en extraire une liste de filerie, ce qui est le plus intéressant et utile pour le futur?
C'est ce qui est AMHA le plus important mais cela demande beaucoup de temps il faut éditer chaque contact et en créer autant que la norme l'exige, entrer le numéro de chaque terminal sur chaque borne ensuite ajouter un champ texte fixe pour étiqueter chaque borne.
Voir ce long sujet : https://qelectrotech.org/forum/viewtopic.php?id=2486
Joshua wrote:
Bon j’arrive un peu en retard sur le sujet….
Bon alors déjà écrire les choses en dure dans le code c’est non. Je comprends bien que dans un premier temps ça arrange tout le monde, mais ensuite après plusieurs versions on veut faire un truc avec plus d’automatisation et/ou poussé tout en gardant la rétrocompatibilité et là je me casse les dents un truc de fou, et de plus du côté utilisateur il y a toujours des pertes qui se produisent….
Aujourd’hui la seule bonne manière c’est à l’utilisateur de faire tous les types de contact dans sa propre collection. Donc pour donner mon avis c’est non pour mettre tous ça dans la collection officielle. QElectroTech semble maintenant pas mal utilisé (aux vues des retours que l’on a) et tout le monde s’accommode de cette lacune donc ça continuera ainsi. Je préfère 1000x ne rien coder (et encore plus si c’est coder un truc « en attendant mieux ») mais une fois lancer faire un truc complet, solide et réfléchie ensemble.
Ensuite voici comment je ferais la chose, et j’y ai déjà réfléchi par le passé.Il faut que les bornes d’élément possèdent plus de propriété et pas que pour les contacts, ainsi on sait quoi faire avec la borne (ça résous déjà le problème que soulève galexis au sujet des contacts inverseurs) il faut que les bornes possèdent leurs propres textes (résous le problème des rotations de texte).
Avoir en dehors du code (un fichier) la liste des numéros de borne de contact, là je m’avance, mais je pense que les numéros sont standard relais / contacteur / bloc aux / bloc aux tempo peut importe la marque. Si c’est bien le cas alors ça rend les choses plus faciles, car il suffit d’incrémenter les numéros de contact au fur et à mesure.*Avoir les numéros de contact et connaître le standard permet aussi de savoir si le nombre de contact liée à un maître est cohérent (actuellement on peut bien avoir 100 contacts esclave sans sourciller). Alors oui cela pourrait sembler secondaire, mais je sais que ce sera demandé un jour donc autant tout bien faire dès le début.
Il y a sûrement des choses que j’oublie mais voila l’idée.Je peux peut-être sembler pénible mais avec l’expérience je sais que c’est une très grosse erreur de faire un truc qu’à moitié. Je ne compte plus le temps que j’ai perdu et la dette technique à cause de chose qu’on a mal fait et/ou pas très poussé, car on voulait rester simple, puis que j’ai repris car QElectroTech à évoluer et nos/vos exigences aussi.
Pour rebondir sur le sujet du paragraphe avec l’étoile *, avec le peu de vrai schéma que je fais, à chaque fois je me rends compte d’une chose qui manque c’est la possibilité (une fonctionnalité) de vérifier que le schéma est valide c’est-à-dire sans être exhaustif : tous les conducteurs ont un nom, tous les contacts sont liés à un esclave (et donc aussi que le nombre de contact est correct), toutes les bornes sont attribuées à un groupe de bornes, tous les éléments ont un label.
Je suis surpris que personne n’a jamais fait cette demande (ou alors j’ai oublié).Pfiu quel pavé
Voir https://qelectrotech.org/forum/viewtopi … 031#p20031
et https://qelectrotech.org/forum/viewtopi … 055#p22055
Cordialement,
Laurent
24 2025-11-08 20:53:40
Re: Qt 6.0 development and qelectrotech (138 replies, posted in Code)
desaparecido wrote:
oh merci .. version master installé (qt5) .. je n'avais plus packages avec qt5 donc j'ai directement essayé la version qt6, je vais rester attentif à l'évolution, là je fait des test avec l'import des .DXF .. pff .. pas donné, merci pour votre travail
scorpio810 wrote:@desaparecido: pour information, la branche qt6-cmake est tres loin d’être stable pour la production, je te conseillerai plutôt la branche master basée sur Qt 5.15!
https://github.com/qelectrotech/qelectr … /qt6-cmake
This branch is 61 commits ahead of, 136 commits behind master.git checkout master rm -Rf build mkdir build && cd build qmake ../qelectrotech.pro time make -j48
Salut Desaparecido,
si tu veux faire des tests je te conseilles de jeter un œil au travail giganteste de Oneil sur son fork github (IA?), je suis vraiment bluffé, et je le remercie grandement pour tous ce travail et ces analyses, certes certains forks que j'ai compilé rapidement comme aspect-ratio-folio cassent mes anciens projets..mais son travail et son analyse mérites d’êtres saluées., chapeau Oneil
https://github.com/EmilOsvoll/qelectrot … hes/active
25 2025-11-07 11:20:44
Re: Share the elements library (14 replies, posted in Elements)
Hello Pierre,
https://github.com/qelectrotech/qelectrotech-elements and https://github.com/qelectrotech/qelectr … nt-contrib
This repository is based on GIT, so you can easily clone and use it with a simple ‘git pull’ command in your local folders to update all items to the main version. You can also create a push request to send your work items.
Only qelectrotech-elements git branch was synced to to QET master branchs when we use
git submodule update --remote elements
git add elements/
And pushed to QET master branch for new packages.
Laurent