MantisBT - Issues

0000340: PDF text appears artificially bold in Adobe Acrobat after migration to Qt 6

Thu, 08 Oct 2026 18:50:32 +0200

Since QElectroTech migrated from Qt 5 to Qt 6, small text in exported PDF files appears excessively thick or artificially bold in Adobe Acrobat Reader at certain zoom levels. When zooming in, the text is rendered correctly.

The same PDF is displayed correctly in Google Chrome and PDFX. Disabling text smoothing in Acrobat makes the text excessively thin, while disabling “Enhance thin lines” has no effect. PDF files exported from the previous Qt 5 version did not show this behavior.

This appears to be a rendering compatibility issue between the PDF output produced with Qt 6 and Adobe Acrobat Reader.

0000253: Terminals position on each element is random.

Wed, 07 Oct 2026 09:43:41 +0200

Hi,

On diagram editor terminal positon of elements are "random". In element editor everything is fine.

I even reinstalled QET but without effect :(

0000112: No snap when zoomed out OR selection is big

Sun, 04 Oct 2026 02:32:08 +0200

Try attached element.
( It is a ruler to replace the built in headers - They are beautiful, but sometimes consume too much paper area...)

1) just open that file, Ctrl-A to select everything, and move it a bit: no snap.
At least here on my screen it is zoomed to

2) When zoomed out much so grid get invisible, it does not snap.
This is unexpected so user may place object off snap.
Best solution would be that neither grid not snapping ever get shut off, just continue getting bigger: 10px -> 20 px -> 50px...

0000344: Incorrect and inconsistent behavior of conductor texts (Conductor Text / Text Formula)

Sun, 04 Oct 2026 02:31:20 +0200

Conductor texts (Conductor Text / Text Formula) behave inconsistently and unpredictably under certain editing conditions. Two separate issues have been observed: unwanted movement of conductor text after editing a junction, and conductor text disappearing completely when used with references.

1) Conductor text changes position after editing a junction
When modifying an existing conductor — for example by adding a branch or adjusting its geometry — the text assigned to the original conductor unexpectedly moves to the new junction or to another segment of the conductor.

Expected behavior:
The conductor text should remain exactly where the user placed it unless the user explicitly moves it.

Actual behavior:
The conductor text relocates automatically after editing the conductor’s geometry.

2) Conductor text disappears when using references
When a conductor contains a reference (e.g., cross‑reference or link), the conductor text sometimes disappears completely.
Once it disappears, it cannot be restored by any action:

changing conductor properties
toggling Text Formula
moving the text
saving and reopening the project
switching between Qt5/Qt6 builds

The text still exists in the conductor object, but it is not rendered.

Expected behavior:
Conductor text should always be displayed if it is defined.

Actual behavior:
Conductor text occasionally becomes invisible and cannot be forced to reappear.

My configuration (important for reproduction)

I do not use automatic conductor texts.

“Show one text per folio potential” is disabled.

0000104: Another crash when saving * with debug screenshot *

Fri, 02 Oct 2026 10:47:15 +0200

r4736
I had been playing with sheet referencing: creating, modifying, deleting
also signals got created and deleted.
Then i pressed the diskette icon, bang!

0000136: Hang at connection folio ref to one more element, with other conductors

Fri, 02 Oct 2026 09:42:05 +0200

r4884
I was linking signals, and realised i should reconnect one, so i was adding a conductor like seen in the screenshot (dotted black line), and qet stopped responding, see screenshot of QtDesigner from where i launched it.

0000137: Crash when making connector

Fri, 02 Oct 2026 09:42:02 +0200

r4895
I delete a conductor and make another -> crash
Repeatable 100% doing like on the attached video in that file, which i have saved if you need.
(note to self: IVL Sheman-31.qet)

I have not yet seen it happening when i do like that on other elements/conductors
If time permit i will try to make a small project and see what makes this happen.

0000095: Collections pane project titles do not fall back to show filename when title is not defined.

Fri, 02 Oct 2026 09:31:58 +0200

...instead it show "Untitled project"

This is unlike Project pane which show filename when title is not defined.

And unlike the displaying of elements that also is displayed by filename when they have no name in a recognised translation.

svn 4734

0000217: Mémoire d'entrée dans les informations éléments

Fri, 02 Oct 2026 09:31:55 +0200

Lors de l'édition des informations beaucoup d'informations sont les mêmes d'un éléments à un autre. Par exemple fournisseur, fabricant, ref etc..
Une mémorisation des entrées précédentes permettrait de gagner en temps pour renseigner ces informations.
On pourrait imaginer qu'une fois une information renseignée pour un élément celle-ci soit disponible dans une liste déroulante pour chacun des autres éléments du schéma.

0000345: The application crashes when opening certain QElectroTech projects

Fri, 02 Oct 2026 09:31:52 +0200

Description
I encountered repeated crashes when trying to open specific QElectroTech project files. The application closes instantly without showing any error dialog. Other projects open normally, so the issue appears to be related to the content or structure of certain project files.

0000240: Au démarrage, apparition d'un message de restauration de fichier entraînant un crash.

Fri, 02 Oct 2026 04:31:41 +0200

Suite à un précédent crash de qElectrotec (je ne connais plus la raison exact), le logiciel me propose de restaurer les fichiers pour les récupérer. Je l'ai fait la première fois, sauf que les fichiers étaient en lecture seul. J'ai donc supprimé ce fichier puis pris une sauvegarde qui était dans un de mes SSD (que je fais manuellement).

Le problème est que maintenant, à chaque fois que je démarre qElectrotec, ce message apparaît toujours.
A ce moment là, deux possibilités:
1. Fermer ce message via la croix -> le logiciel démarre normalement ensuite
2. Appuyer sur "Ok" -> un message d'erreur s'affiche -> le logiciel crash

En soit ce bug n'empêche donc en rien l'utilisation du logiciel, mais c'est un peu pénible que la fenêtre s'affiche à chaque démarrage. A noter que j'ai aussi essayé de désinstaller le logiciel pour réinstaller la dernière version dev. Cela n'a pas empêché le message de s'afficher.

En annexe, vous trouverez des captures d'écran des évènements.

0000256: composite text folio reference overlapped

Thu, 01 Oct 2026 05:34:35 +0200

Hello,
composite text from folio reference overlapped only on coming arrow, going arrow work as it should.
No matter how it is oriented in element editor and on diagram editor.

0000338: Win-versions contain wrong Elements-license

Thu, 01 Oct 2026 05:18:48 +0200

The windows-versions in installer and Ready-To-Use - Package contain another ELEMENTS.LICENSE than in the source-directory on GitHub!
The file at GitHub is significantly more up-to-date and contains more language versions!

This also applies to these files:
- README
- README.md
- ChangeLog
- CREDIT

0000211: Charset-Issue on current installer (0.8-RC)

Thu, 01 Oct 2026 05:13:03 +0200

Current installer seems to have an issue with German umlauts (see screenshot). It should read "Zeichnungsköpfe". If issue cannot be fixed within the installer, I recommend rewriting the German umlaut and use "Zeichnungskoepfe" within the installer. This is quite common if such problems occure.

0000147: Missing translation to German when copying elements

Thu, 01 Oct 2026 05:13:01 +0200

In the element editor, when copying an element, the menu item is named "Copier" instead of "Kopieren" when using German.

Version: Version 0.6 (RC3) +svn5146

0000193: Error in italian traslate

Thu, 01 Oct 2026 05:12:59 +0200

in italian version I found under Generale/progetti

- Sentence in francais: " Position de la liste des....."
- Word non correct "Salvatoaggio", word correct is "Salvataggio" without "o"

0000343: 0.100 : file contents is not consistently saved the same way for the same visual

Thu, 01 Oct 2026 05:12:54 +0200

I have this file at work using custom elements.
I created an extract for reproducibility attached here : https://github.com/ThomasPrioul/test-qet-export-diff

Whenever I close/open and save the file, the whole file is mixed up :
- attributes order
- elements order

So it's very hard to track diffs in git, it creates huge commits for nothing.
I can't reproduce the behavior on an empty new file where diffs seems much simpler.

0000105: Conductors at angle instead of orthogonal - with steps to reproduce

Thu, 01 Oct 2026 02:29:25 +0200

r4748

0000101: Crash and other issues when editing an arc * REPEATABLE *

Thu, 01 Oct 2026 02:27:26 +0200

r4736
See Steps To Reproduce

0000133: The location field shown at element sometimes do not show last line

Tue, 29 Sep 2026 05:18:22 +0200

r4836, but i have seen this earlier too.

Workaround: user enters a bunch of spaces after last word -> line shows up

0000188: %projectfilename variable

Tue, 29 Sep 2026 04:58:18 +0200

When using the variable %projectfilename in title block, it works perfect in all folios but in summary is not showing up.

0000237: A "-" in label of user elements causes line feed

Fri, 25 Sep 2026 11:47:27 +0200

If you create a user element (or copy a default element and save as user element) "-" in label will cause a line feed.
"-" in a label is essential as it is the default prefix. This must not cause a line feed.
It should be like "=P+L-A" but it results in
"=P+L-
A"
with line feed!

0000229: [AppImage] crash by right-click on conductor's control point

Fri, 25 Sep 2026 11:47:25 +0200

When I right-click on a control point (blue point) of a selected conductor, the program crashes.
It's easier to reproduce after zooming in the schema.
Problem occurs on Ubuntu 20.04 with AppImage (QElectroTech_0.8-DEV-r7117-x86_64.AppImage).
Could not reproduce on Windows version.

0000278: Crash on edit element : save as... i have wrong... save> crash

Fri, 25 Sep 2026 10:37:26 +0200

Modify element
(even without modification) by moving a eur line putting it in its place, it activates save & save as.
click on save as.
oops... i was wrong...
cancel
click on save!
> crash program
change (even without changing) by moving a single row to make it active again save and save as.
click on save as.
oops... i was wrong...
Cancel
click on save!
> program blocked
three days ago I installed version 7728 and it's much improved (crashes during work didn't repeat as often happened).
I tried it on this, but the crash remains...

report generated Macos (one part):
Process: qelectrotech [2560]
Path: /Applications/qelectrotech.app/Contents/MacOS/qelectrotech
Identifier: org.qelectrotech
Version: 0.90-DEV r7728 (0)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: qelectrotech [2560]
User ID: 501
Date/Time: 2022-12-10 16:25:18.258 +0100
OS Version: Mac OS X 10.15.7 (19H2026)
Report Version: 12
Anonymous UUID: 796A414F-1A45-54CC-19D8-0FC1D728748E

Time Awake Since Boot: 18000 seconds
System Integrity Protection: enabled
Crashed Thread: 7 Thread (pooled)
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000499acb3d64f8
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [2560]
VM Regions Near 0x499acb3d64f8:
mapped file 0000000142ff6000-0000000143eb6000 [ 14.8M] rw-/rwx SM=COW
-->
MALLOC_NANO 0000600000000000-0000600008000000 [128.0M] rw-/rwx SM=ALI
Thread 0:: Dispatch queue: com.apple.main-thread
0 org.qelectrotech 0x000000010f5324d9 0x10f27d000 + 2839769
1 org.qt-project.QtGui 0x00000001104f8ba7 QStandardItem::~QStandardItem() + 119
2 org.qelectrotech 0x000000010f532503 0x10f27d000 + 2839811
3 org.qt-project.QtGui 0x00000001104f8ba7 QStandardItem::~QStandardItem() + 119
4 org.qelectrotech 0x000000010f532503 0x10f27d000 + 2839811
5 org.qt-project.QtGui 0x00000001104f8ba7 QStandardItem::~QStandardItem() + 119
6 org.qelectrotech 0x000000010f532503 0x10f27d000 + 2839811
7 org.qt-project.QtGui 0x00000001104f8ba7 QStandardItem::~QStandardItem() + 119
8 org.qelectrotech 0x000000010f532503 0x10f27d000 + 2839811
9 org.qt-project.QtGui 0x00000001104f8ba7 QStandardItem::~QStandardItem() + 119
10 org.qt-project.QtGui 0x00000001104f8e2e QStandardItem::~QStandardItem() + 14
11 org.qt-project.QtGui 0x00000001104fb487 QStandardItemModel::~QStandardItemModel() + 199
12 org.qelectrotech 0x000000010f63171e 0x10f27d000 + 3884830
13 org.qt-project.QtCore 0x0000000110bc3f01 QObjectPrivate::deleteChildren() + 289
14 org.qt-project.QtWidgets 0x000000010fbc1ac4 QWidget::~QWidget() + 1108
15 org.qt-project.QtWidgets 0x000000010fe7162e QTreeView::~QTreeView() + 14
16 org.qt-project.QtCore 0x0000000110bc3f01 QObjectPrivate::deleteChildren() + 289
17 org.qt-project.QtWidgets 0x000000010fbc1ac4 QWidget::~QWidget() + 1108
18 org.qelectrotech 0x000000010f61b45f 0x10f27d000 + 3794015
19 org.qelectrotech 0x000000010f2cf5bd 0x10f27d000 + 337341
20 org.qelectrotech 0x000000010f2cf616 0x10f27d000 + 337430
21 org.qelectrotech 0x000000010f4c9e50 0x10f27d000 + 2412112
22 org.qelectrotech 0x000000010f62cd93 0x10f27d000 + 3866003
23 org.qelectrotech 0x000000010f62d3ae 0x10f27d000 + 3867566
24 org.qt-project.QtCore 0x0000000110bcc57f 0x1109b1000 + 2209151
25 org.qt-project.QtWidgets 0x000000010fb8d446 QAction::activate(QAction::ActionEvent) + 310
26 org.qt-project.QtWidgets 0x000000010fc80f70 0x10fb86000 + 1027952
27 org.qt-project.QtWidgets 0x000000010fc8216e QAbstractButton::mouseReleaseEvent(QMouseEvent*) + 270
28 org.qt-project.QtWidgets 0x000000010fd8298f QToolButton::mouseReleaseEvent(QMouseEvent*) + 15
29 org.qt-project.QtWidgets 0x000000010fbd254b QWidget::event(QEvent*) + 443
30 org.qt-project.QtWidgets 0x000000010fd83148 QToolButton::event(QEvent*) + 312
31 org.qt-project.QtWidgets 0x000000010fb96966 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 262
32 org.qt-project.QtWidgets 0x000000010fb99614 QApplication::notify(QObject*, QEvent*) + 6916
33 org.qt-project.QtCore 0x0000000110b9b0a7 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 167
34 org.qt-project.QtWidgets 0x000000010fb97262 QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) + 882
35 org.qt-project.QtWidgets 0x000000010fbf138e 0x10fb86000 + 439182
36 org.qt-project.QtWidgets 0x000000010fbefb1f 0x10fb86000 + 432927
37 org.qt-project.QtWidgets 0x000000010fb96966 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 262
38 org.qt-project.QtWidgets 0x000000010fb97ced QApplication::notify(QObject*, QEvent*) + 477
39 org.qt-project.QtCore 0x0000000110b9b0a7 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 167
40 org.qt-project.QtGui 0x00000001101734ec QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) + 3500
41 org.qt-project.QtGui

at 23.18 crash on work (report on work)
best regards.
Tiziano

0000273: Si blocca come se stesse facendo un salvataggio

Thu, 24 Sep 2026 22:36:45 +0200

QElectroTech V 0.90-DEV+0d90defcfb0a58100c957a06d79751d3
Si blocca come se stesse eseguendo un salvataggio, ma succede frequentemente.
Il mio PC è così composto:
Edizione: Windows 11 Home
Versione:22H2
Build sistema operativo: 22621.608
Esperienza: Windows Feature Experience Pack 1000.22634.1000.0