• scorpio810
  • scorpio810
  • QElectroTech Team Manager, Developer, Packager
  • Offline

Re: Qt 6.0 development and qelectrotech

Re-searcher wrote:

@scorpio810

Merci pour l'information.
Thanks for the information.


https://github.com/qelectrotech/qelectr … angeLog.MD

github_changelog_generator -u qelectrotech --token xxxxxxxxxxxxxxxxxxxxxxxxxxxx -p qelectrotech-source-mirror --base "" --since-tag= 543447aa31f42525967ed26223d2d388ecb6c55b --output ChangeLog.MD


git shortlog $(git describe --tags --abbrev=0)..HEAD > file3.txt
git log $(git describe --tags --abbrev=0)..HEAD --pretty=format:"%ar : %s , %an" > file4.txt
git log --graph --pretty=format:'%Cred%h%Creset -%C(yellow)%d%Creset %s %Cgreen(%cr) %C(bold blue)<%an>%Creset' --abbrev-commit > file8.txt
vi command :968,$d to delete lines after line 968!

Post's attachments

Attachment icon file3.txt 39.68 kb, 182 downloads since 2025-09-21 

Attachment icon file4.txt 61.45 kb, 217 downloads since 2025-09-21 

Attachment icon file8.txt 74.34 kb, 226 downloads since 2025-09-21 

"Le jour où tu découvres le Libre, tu sais que tu ne pourras jamais plus revenir en arrière..."Questions regarding QET belong in this forum and will NOT be answered via PM! – Les questions concernant QET doivent être posées sur ce forum et ne seront pas traitées par MP !

127 Reply by Re-searcher (edited by Re-searcher 2025-09-28 13:00:13)

Re: Qt 6.0 development and qelectrotech

Y a-t-il actuellement des personnes qui travaillent à la programmation de Qt5 vers Qt6 ?
Are there people currently working on programming Qt5 to Qt6?
Zijn er personen die nu bezig zijn met het programmeren van Qt5 naar Qt6 ?


Où puis-je trouver les nouveaux fichiers pour Qt6 ?
Where can I find the new files for Qt6?
Waar kan ik de nieuwe bestanden vinden voor Qt6 ?

I am an pre-retired industrial developer technician and born in 1960.Electrical, Electronics, Mechanical,Électricité, électronique, mécanique,Native language(Dutch)/langue maternelle/moedertaal(BE,NL).OS : Linux/GNU Debian Forky/Sid and Trixie; Desktop: xfce4 ; Qt 5 and 6; Compiler :  qmake(Qt5) qmake6(Qt6)
  • scorpio810
  • scorpio810
  • QElectroTech Team Manager, Developer, Packager
  • Offline

Re: Qt 6.0 development and qelectrotech

git clone --recursive https://github.com/qelectrotech/qelectrotech-source-mirror.git
cd qelectrotech-source-mirror/
git switch qt6-cmake

comment line 137 of /sources/machine_info.cpp to compile.

mkdir build && cd build
cmake .. -G Ninja -DBUILD_WITH_QT6=ON
time ninja -j48

Ignored 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 qelectrotech

real    0m36,019s
user    21m37,065s
sys     1m39,485s



QElectroTech 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)


https://download.qelectrotech.org/qet/forum_img_2/Qt6_test_build.png

"Le jour où tu découvres le Libre, tu sais que tu ne pourras jamais plus revenir en arrière..."Questions regarding QET belong in this forum and will NOT be answered via PM! – Les questions concernant QET doivent être posées sur ce forum et ne seront pas traitées par MP !
  • scorpio810
  • scorpio810
  • QElectroTech Team Manager, Developer, Packager
  • Offline

Re: Qt 6.0 development and qelectrotech

Re-searcher wrote:

Y a-t-il actuellement des personnes qui travaillent à la programmation de Qt5 vers Qt6 ?
Are there people currently working on programming Qt5 to Qt6?
Zijn er personen die nu bezig zijn met het programmeren van Qt5 naar Qt6 ?

See: https://qelectrotech.org/forum/viewtopi … 035#p22035

"Le jour où tu découvres le Libre, tu sais que tu ne pourras jamais plus revenir en arrière..."Questions regarding QET belong in this forum and will NOT be answered via PM! – Les questions concernant QET doivent être posées sur ce forum et ne seront pas traitées par MP !

Re: Qt 6.0 development and qelectrotech

Debian 13 = Trixie
GCC = 14.2.0
Qt = 6.8.2+dfsg
Kernel : 6.12.48+deb13-amd64


avec cmake = erreur de compilation
avec qmake6 = compilation

with cmake = build error
with qmake6 = build


QElectroTech V 0.100.0-dev
Compilation : GCC 14.2.0
Built with Qt 6.8.2 - x86_64 - Date : Sep 28 2025 : 16:08:57
Git Revision : 411fb3c4dc54b6aaea00f034d6c5396de5daa474
Run with Qt 6.8.2 using 2 thread(s)
CPU : model name : Intel(R) Core(TM)2 Duo CPU P8600 @ 2.40GHz
RAM Total : 3 GB
RAM Available : 2 GB
GPU : Advanced Micro Devices, Inc. [AMD/ATI] RV635/M86 [Mobility Radeon HD 3650]
GPU RAM : Video memory: 256MB Dedicated video memory: 256 MB Currently available dedicated video memory: 255 MB
OS : linux - x86_64 - Version : Debian GNU/Linux 13 (trixie) - Kernel : 6.12.48+deb13-amd64
*** Qt screens ***
( 1 : 1680 x 1050 )

I am an pre-retired industrial developer technician and born in 1960.Electrical, Electronics, Mechanical,Électricité, électronique, mécanique,Native language(Dutch)/langue maternelle/moedertaal(BE,NL).OS : Linux/GNU Debian Forky/Sid and Trixie; Desktop: xfce4 ; Qt 5 and 6; Compiler :  qmake(Qt5) qmake6(Qt6)

Re: Qt 6.0 development and qelectrotech

../sources/colorbutton.cpp: In member function ‘void ColorButton::clicked(bool)’:
../sources/colorbutton.cpp:56:32: warning: unused parameter ‘checked’ [-Wunused-parameter]
   56 | void ColorButton::clicked(bool checked)
      |                           ~~~~~^~~~~~~



../sources/colorcombobox.cpp: In member function ‘virtual void ColorComboBox::paintEvent(QPaintEvent*)’:
../sources/colorcombobox.cpp:80:45: warning: unused parameter ‘e’ [-Wunused-parameter]
   80 | void ColorComboBox::paintEvent(QPaintEvent *e) {
      |                                ~~~~~~~~~~~~~^


../sources/editor/UndoCommand/openelmtcommand.cpp: In member function ‘virtual void OpenElmtCommand::redo()’:
../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")
      |                                                                                                      ^

I am an pre-retired industrial developer technician and born in 1960.Electrical, Electronics, Mechanical,Électricité, électronique, mécanique,Native language(Dutch)/langue maternelle/moedertaal(BE,NL).OS : Linux/GNU Debian Forky/Sid and Trixie; Desktop: xfce4 ; Qt 5 and 6; Compiler :  qmake(Qt5) qmake6(Qt6)
  • scorpio810
  • scorpio810
  • QElectroTech Team Manager, Developer, Packager
  • Offline

Re: Qt 6.0 development and qelectrotech

Maybe with Debian Trixie, compile ok on Debian unstable.
GCC 15.2.0 with Qt 6.9.2 ...

@Erik: What time you need to compile QET on this old CPU : model name : Intel(R) Core(TM)2 Duo CPU P8600 @ 2.40GHz?

"Le jour où tu découvres le Libre, tu sais que tu ne pourras jamais plus revenir en arrière..."Questions regarding QET belong in this forum and will NOT be answered via PM! – Les questions concernant QET doivent être posées sur ce forum et ne seront pas traitées par MP !

Re: Qt 6.0 development and qelectrotech

@Laurent
Toutes mes condoléances pour la perte de votre chien.
Je comprends très bien ce que vous vivez.
Mon frère et moi n'avons pas d'enfants. Mon frère a des poneys (petits chevaux). Deux d'entre eux sont morts à cause d'une attaque de loups. J'allais voir ces poneys (petits chevaux) tous les jours. Je n'arrive toujours pas à comprendre que ces loups soient protégés par l'Europe.


CPU : model name : Intel(R) Core(TM)2 Duo CPU P8600 @ 2.40GHz

make -j2

real    37m45.343s
user    70m25.357s
sys    4m10.749s

I am an pre-retired industrial developer technician and born in 1960.Electrical, Electronics, Mechanical,Électricité, électronique, mécanique,Native language(Dutch)/langue maternelle/moedertaal(BE,NL).OS : Linux/GNU Debian Forky/Sid and Trixie; Desktop: xfce4 ; Qt 5 and 6; Compiler :  qmake(Qt5) qmake6(Qt6)

Re: Qt 6.0 development and qelectrotech

scorpio810 wrote:
git clone --recursive [url]https://github.com/qelectrotech/qelectrotech-source-mirror.git[/url]
cd qelectrotech-source-mirror/
git checkout qt6-cmake

comment line 137 of /sources/machine_info.cpp to compile.

mkdir build && cd build
cmake .. -G Ninja -DBUILD_WITH_QT6=ON
time ninja -j48


QElectroTech 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)

merci beaucoup pour ces infos ! build OK avec CMAKE,  ma machine est sur cachy0S à jour (basé sur Archlinux).  Je verrais si je prend le temps pour tester avec QMAKE6.  et merci aux développeurs pour ce projet.

QElectroTech V 0.100.0-dev
Compilation : GCC 15.2.1 20250813
Built with Qt 6.10.0 - x86_64 - Date : Oct 25 2025 : 16:47:49
Git Revision : 411fb3c4dc54b6aaea00f034d6c5396de5daa474 
Run with Qt 6.10.0 using 16 thread(s)
CPU : model name : AMD Ryzen 7 PRO 7840U w/ Radeon 780M Graphics 
RAM Total : 23 GB
RAM Available : 16 GB
GPU : Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 (rev dd) 
GPU RAM : Video memory: 8192MB Dedicated video memory: 8192 MB Currently available dedicated video memory: 6822 MB 
OS : linux - x86_64 - Version : CachyOS - Kernel : 6.17.5-2-cachyos
*** Qt screens *** 
( 1 : 1920 x 1200 ) 
( 2 : 3440 x 1440 ) 
( 3 : 2560 x 1440 )

  • scorpio810
  • scorpio810
  • QElectroTech Team Manager, Developer, Packager
  • Offline

Re: Qt 6.0 development and qelectrotech

@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

"Le jour où tu découvres le Libre, tu sais que tu ne pourras jamais plus revenir en arrière..."Questions regarding QET belong in this forum and will NOT be answered via PM! – Les questions concernant QET doivent être posées sur ce forum et ne seront pas traitées par MP !

136 Reply by Re-searcher (edited by Re-searcher 2025-10-30 20:09:36)

Re: Qt 6.0 development and qelectrotech

OS : GNU/Linux forky/sid

Il y a des erreurs dans le master (9e78dc5)
There are errors in the master (3cf9095)

/sources/qgpimanager.h

g++ -c -pipe -std=c++17 -O2 -std=gnu++1z -Wall -Wextra -D_REENTRANT -DQET_ALLOW_OVERRIDE_CED_OPTION -DQET_ALLOW_OVERRIDE_CTBTD_OPTION -DQET_ALLOW_OVERRIDE_CD_OPTION -DQET_ALLOW_OVERRIDE_DD_OPTION -DQET_EXPORT_PROJECT_DB -DQAPPLICATION_CLASS=QApplication -DQT_MESSAGELOGCONTEXT -DGIT_COMMIT_SHA=\"9e78dc56a87f3dda73e4980165ab60927495ebcd\" -DQET_LANG_PATH=/usr/local/share/qelectrotech/lang/ -DQET_COMMON_COLLECTION_PATH=/usr/local/share/qelectrotech/elements/ -DQET_COMMON_TBT_PATH=/usr/local/share/qelectrotech/titleblocks/ -DQT_NO_DEBUG -DQT_SVG_LIB -DQT_PRINTSUPPORT_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_XML_LIB -DQT_SQL_LIB -DQT_CONCURRENT_LIB -DQT_CORE_LIB -I../../qelectrotech-source-mirror-9e78dc5 -I. -I../SingleApplication -I../sources/ui -I/usr/include/KF6/KCoreAddons -I/usr/include/KF6/KWidgetsAddons -I../sources/TerminalStrip/ui -I/usr/include/x86_64-linux-gnu/qt6 -I/usr/include/x86_64-linux-gnu/qt6/QtSvg -I/usr/include/x86_64-linux-gnu/qt6/QtPrintSupport -I/usr/include/x86_64-linux-gnu/qt6/QtWidgets -I/usr/include/x86_64-linux-gnu/qt6/QtGui -I/usr/include/x86_64-linux-gnu/qt6/QtNetwork -I/usr/include/x86_64-linux-gnu/qt6/QtXml -I/usr/include/x86_64-linux-gnu/qt6/QtSql -I/usr/include/x86_64-linux-gnu/qt6/QtConcurrent -I/usr/include/x86_64-linux-gnu/qt6/QtCore -Irelease -I. -I/usr/lib/x86_64-linux-gnu/qt6/mkspecs/linux-g++ -o release/conductorautonumerotation.o ../sources/conductorautonumerotation.cpp
In file included from ../sources/diagram.h:28,
                 from ../sources/bordertitleblock.cpp:21:
../sources/qgimanager.h:52:14: error: ‘void QGIManager::manage(QVector<QGraphicsItem*>&)’ cannot be overloaded with ‘void QGIManager::manage(const QList<QGraphicsItem*>&)’
   52 |         void manage(const QVector<QGraphicsItem *> &items);
      |              ^~~~~~
../sources/qgimanager.h:49:22: note: previous declaration ‘void QGIManager::manage(const QList<QGraphicsItem*>&)’
   49 |                 void manage(const QList<QGraphicsItem *> &);
      |                      ^~~~~~
../sources/qgimanager.h:53:14: error: ‘void QGIManager::release(QVector<QGraphicsItem*>&)’ cannot be overloaded with ‘void QGIManager::release(const QList<QGraphicsItem*>&)’
   53 |         void release(const QVector<QGraphicsItem *> &items);
      |              ^~~~~~~
../sources/qgimanager.h:51:22: note: previous declaration ‘void QGIManager::release(const QList<QGraphicsItem*>&)’
   51 |                 void release(const QList<QGraphicsItem *> &);
      |                      ^~~~~~~
make[1]: *** [Makefile.Release:4515: release/bordertitleblock.o] Error 1
make[1]: *** Waiting for unfinished jobs....
In file included from ../sources/diagram.h:28,
                 from ../sources/conductorautonumerotation.cpp:23:
../sources/qgimanager.h:52:14: error: ‘void QGIManager::manage(QVector<QGraphicsItem*>&)’ cannot be overloaded with ‘void QGIManager::manage(const QList<QGraphicsItem*>&)’
   52 |         void manage(const QVector<QGraphicsItem *> &items);
      |              ^~~~~~
../sources/qgimanager.h:49:22: note: previous declaration ‘void QGIManager::manage(const QList<QGraphicsItem*>&)’
   49 |                 void manage(const QList<QGraphicsItem *> &);
      |                      ^~~~~~
../sources/qgimanager.h:53:14: error: ‘void QGIManager::release(QVector<QGraphicsItem*>&)’ cannot be overloaded with ‘void QGIManager::release(const QList<QGraphicsItem*>&)’
   53 |         void release(const QVector<QGraphicsItem *> &items);
      |              ^~~~~~~
../sources/qgimanager.h:51:22: note: previous declaration ‘void QGIManager::release(const QList<QGraphicsItem*>&)’
   51 |                 void release(const QList<QGraphicsItem *> &);
      |                      ^~~~~~~
make[1]: *** [Makefile.Release:4563: release/conductorautonumerotation.o] Error 1
make[1]: Leaving directory '/home/me/me/QET/qelectrotech-source-mirror-9e78dc5/build'
make: *** [Makefile:42: release] Error 2
me@me:~/me/QET/qelectrotech-source-mirror-9e78dc5/build$

I am an pre-retired industrial developer technician and born in 1960.Electrical, Electronics, Mechanical,Électricité, électronique, mécanique,Native language(Dutch)/langue maternelle/moedertaal(BE,NL).OS : Linux/GNU Debian Forky/Sid and Trixie; Desktop: xfce4 ; Qt 5 and 6; Compiler :  qmake(Qt5) qmake6(Qt6)

Re: Qt 6.0 development and qelectrotech

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

  • scorpio810
  • scorpio810
  • QElectroTech Team Manager, Developer, Packager
  • Offline

Re: Qt 6.0 development and qelectrotech

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 nomicons/wink
https://github.com/EmilOsvoll/qelectrot … hes/active

"Le jour où tu découvres le Libre, tu sais que tu ne pourras jamais plus revenir en arrière..."Questions regarding QET belong in this forum and will NOT be answered via PM! – Les questions concernant QET doivent être posées sur ce forum et ne seront pas traitées par MP !

139 Reply by Re-searcher (edited by Re-searcher 2025-11-17 16:17:20)

Re: Qt 6.0 development and qelectrotech

@ scorpio810
@ plc-user

I have also an faster computer,but i use it not for compiling the source.
I have it one year and one month.MSI Raider 18HXA14VGG


Your computers compiling to fast that you not see the errors and the warings.

errors
missing #include <QUuid>
../sources/qetxml.h  = add #include <QUuid> on line 23 after QPen on line 22

../sources/titleblocktemplate.cpp
missing bool on line 106
now on line 106
bool xml_parsing (bool)xml_doc.setContent(&template_file);


../sources/titleblock/templatescollection.cpp
missing bool on  line 457

now on line 457
bool xml_parsing = (bool)xml_document -> setContent(&xml_file);

../sources/titleblock/templateview.h
line 22 #include <QGraphicsGridLayout>
line 23 #include <QGraphicsLayoutItem>

Post's attachments

Attachment icon QET_MSI_2025-11-17_14-49-21.png 94.99 kb, 12 downloads since 2025-11-17 

I am an pre-retired industrial developer technician and born in 1960.Electrical, Electronics, Mechanical,Électricité, électronique, mécanique,Native language(Dutch)/langue maternelle/moedertaal(BE,NL).OS : Linux/GNU Debian Forky/Sid and Trixie; Desktop: xfce4 ; Qt 5 and 6; Compiler :  qmake(Qt5) qmake6(Qt6)

Re: Qt 6.0 development and qelectrotech

Hallo QET-Entwickler!
(English version follows)

Unabhängig von der letzten Änderung bezüglich der font-family haben wir eine Herausforderung!
In den vorhandenen Elementen wird von Qt5 die Schriftart-Information so gespeichert:

font="Liberation Sans,5,-1,5,50,0,0,0,0,0,Regular"

Wenn diese Element-Datei von der Qt6-Version von QElectroTech geöffnet und wieder gespeichert wird, wird die Schriftart-Information wie folgt gespeichert:

font="Liberation Sans,5,-1,5,400,0,0,0,0,0,0,0,0,0,0,1,Regular"

So weit so gut:
Die Schrift wird richtig in das neue Format übersetzt!

Sollte die Projekt- oder Element-Datei, die mit Qt6 gespeichert wurde, mit einer Qt5-Version geöffnet werden, werden die verwendeten Schriftarten nicht erkannt und daher ALLE Schriftarten auf einen Qt6-Standart "Sans Serif" und die Standart-Größe "9" gesetzt!
Dies zerstört im Zweifel also das gute Aussehen der Elemente, die mit der Qt6-Version von QET erstellt bzw. gespeichert wurden!

Wir müssen die Benutzer also darauf hinweisen, daß es keinen (einfachen) Weg gibt, die Projektdateien und die Elemente, die einmal mit der Qt6-Version gespeichert wurden, wieder mit älteren QET-Versionen zu öffnen!

Gruß
  plc-user



Englsh translation:

Hello QET-developers!

Regardless of the latest change about the font family, we have a challenge!
In existing projects and elements, Qt5 stores the font information as follows:

font="Liberation Sans,5,-1,5,50,0,0,0,0,0,Regular"

When this element file is opened and saved again by a Qt6 version of QElectroTech, the font information is stored as follows:

font="Liberation Sans,5,-1,5,400,0,0,0,0,0,0,0,0,0,0,1,Regular"

So far, so good:
The font is correctly converted to the new format!

However, if the project or element file saved with Qt6 is opened with a Qt5 version, the real fonts are not recognised and ALL fonts are set to the Qt standard ‘Sans Serif’ and the standard size ‘9’!
This may/will destroy the good appearance of the elements created/saved with the Qt6 version of QET!

We must therefore point out to users that there is no (easy) way to open project files and elements that were once saved with the Qt6 version using older QET versions!

Best regards
  plc-user

Fragen zu QET gehören in dieses Forum und werden nicht per PM beantwortet! – Questions regarding QET belong in this forum and will NOT be answered via PM! – Les questions concernant QET doivent être posées sur ce forum et ne seront pas traitées par MP !
  • scorpio810
  • scorpio810
  • QElectroTech Team Manager, Developer, Packager
  • Offline

Re: Qt 6.0 development and qelectrotech

Hallo plc-user and thanks you for your research. nomicons/wink

I think we need to add warnings if a project has been saved with the Qt6 Framework  and launched on Qt 5 build of QET, before users can break their projects by mixing Qt5 and Qt 6 versions of QET on the same project!

For now, I only provide Qt5 versions, but what will happen if they compile it themselves with Qt6?

A quick search in the code provides clues to alert the user:
https://github.com/qelectrotech/qelectr … y.cpp#L156

https://github.com/qelectrotech/qelectr … .cpp#L1381


Best regards,
Laurent

"Le jour où tu découvres le Libre, tu sais que tu ne pourras jamais plus revenir en arrière..."Questions regarding QET belong in this forum and will NOT be answered via PM! – Les questions concernant QET doivent être posées sur ce forum et ne seront pas traitées par MP !

Re: Qt 6.0 development and qelectrotech

I have no idea how difficult it is to program this and whether it is even possible, but wouldn't it be possible to automatically create a backup when a .qet file created with qt5 is opened with a qt6 version?

  • scorpio810
  • scorpio810
  • QElectroTech Team Manager, Developer, Packager
  • Offline

Re: Qt 6.0 development and qelectrotech

Kellermorph wrote:

I have no idea how difficult it is to program this and whether it is even possible, but wouldn't it be possible to automatically create a backup when a .qet file created with qt5 is opened with a qt6 version?

No no, just don't open file when you saw these warnings:
Warning: the element " " was saved with a later version of QElectroTech.
Warning: this project" " was saved with a later version of QElectroTech.

Edit: There are already methods in the code to check and alert users if, for example, they open a project saved in version 0.100 on an earlier version.

"Le jour où tu découvres le Libre, tu sais que tu ne pourras jamais plus revenir en arrière..."Questions regarding QET belong in this forum and will NOT be answered via PM! – Les questions concernant QET doivent être posées sur ce forum et ne seront pas traitées par MP !

Re: Qt 6.0 development and qelectrotech

Hello everybody,

scorpio810 wrote:

For now, I only provide Qt5 versions, but what will happen if they compile it themselves with Qt6?

I guess, the Qt6-version will come with an increased version-number, will it?
In that case we should add a warning, when opening an "old" file to choose "save as..." for saving the changes or to create a backup before going on!
If such a warning is also included in Release-Notes puts us developer in a safe position, I guess...!

Kellermorph wrote:

(...) automatically create a backup when a .qet file created with qt5 is opened with a qt6 version?

If there are hints in Release-Notes and an additional warning-message, when loading an "old" file ... I guess that should be enough: After all, the user is responsible for making backup copies of their data.


For the official element collection, we should completely revise the elements for the switch to Qt6. It might help that I already did this for the introduction of the Liberation fonts...

Fragen zu QET gehören in dieses Forum und werden nicht per PM beantwortet! – Questions regarding QET belong in this forum and will NOT be answered via PM! – Les questions concernant QET doivent être posées sur ce forum et ne seront pas traitées par MP !