I was recently doing some work to improve the styling support in dxf2elmt, and while looking at the element files and the QET code, I noticed that the Line and fill colors are stored in the XML as a string with a name such as "red", and "HTMLWhiteFloralWhite", etc.

I was wondering if there was a specific reason this was stored this way, and the colors in the element editor are just a drop down of options, instead of a color picker, and storing the RGB values in the element file?

Was haltet ihr von der Idee? Wenn ihr sagt, dass diese sinnvoll und gut ist, würde ich versuchen diese in den nächsten Monaten so wie ich Zeit habe mithilfe von Chatgpt umzusetzen.

Translate:
Hello everyone,
It has long bothered me that Qelectrotech allows you to connect one master element to an infinite number of slave elements.
Now I have an idea how this could be changed without significantly altering the existing logic.
A checkbox is added to the Component Properties tab in the Component Editor. This is called, for example, “Define max number of slave elements.”
If this is not checked, everything remains as it is.
If it is checked, a text box is activated below where you can define the number.
Next, the existing selection window is expanded to include a tab, e.g., “Full master elements.”
Now, the system checks whether the connections to slave elements are less than the maximum number for the master elements for which the maximum number is defined.
If this is the case, everything remains as it is.
If the number of connections is equal to the maximum number, the master element is moved to the new tab and a connection with it is no longer possible. This would be very helpful in order to prevent a master element from being connected to more slave elements than is actually possible, and the selection window would be tidier as there would no longer be so many entries, which would make working easier.

What do you think of the idea? If you say it makes sense and is good, I would try to implement it in the next few months as I have time with the help of ChatGPT.

Translated with DeepL.com (free version)

Salut Joshua !
Salut Laurent !

English follows below!

Brauchen wir bei QET zufällige Hashes, die irgendwas verschlüsseln, oder so? Die einzigen zufälligen Zahlen, die ich sehe, sind die UUIDs in den Elementen. Aber vielleicht übersehe ich auch etwas...

Grund der Frage:
Die XML-Tags in den Element- und Projekt-Dateien werden bei jedem Abspeichern durcheinandergewürfelt, da die Informationen dazu in Hashes gespeichert werden, deren zugrundeliegende Zufallszahl regelmäßig erneuert wird.
Wenn wir auf die zufällige Sortierung in den Hashes verzichten können, können wir dafür beim Start von QET einen Vorgabewert an Qt geben, sodass die Sortierung der XML-Tags von einem Speichervorgang zum nächsten nicht komplett durcheinandergewürfelt werden!
Bei Projektdateien wird das XML regelmäßig aus der internen SQlite-DB neu erzeugt, und daher sind die Tags nicht immer in derselben Reihenfolge.
Bei Element-Dateien scheint es aber sehr gut zu funktionieren, dass die Tags nicht gemischt werden, wenn die Randomisierung abgeschaltet ist! Auf diese Art werden DIFFs von Element-Dateien nicht so groß, wenn nur eine Kleinigkeit daran geändert wird, wie z.B. das Hinzufügen einer weiteren Sprache.

Einen Patch habe ich in meinem github-repository vorbereitet.

Gruß
  plc-user

English translation:

To the main-developers:

Do we need random hashes with QET that encrypt something or something like that? The only random numbers I see are the UUIDs in the elements. But maybe I'm overlooking something...

Reason for the question:
The XML tags in the element and project files are mixed up every time they are saved, because the information is stored in hashes whose underlying random number is regularly renewed.
If we can do without the random sorting in the hashes, we can give Qt a default value when starting QET so that the sorting of the XML tags is not completely mixed up from one save operation to the next!
For project files, the XML is regularly regenerated from the internal SQlite DB, so the tags are not always in the same order.
However, for element files, it seems to work very well that the tags are not mixed when randomization is turned off! This way, DIFFs of element files do not become so large when only a small change is made, such as adding another language.

I prepared a patch in my github-repository.

Best regards,
  plc-user

erreur de frappe trouvée dans les fichiers

../sources/ui/dynamicelementtextitemeditor.cpp
26 = #include "../ui_dynamicelementtextitemeditor.h"

_  devrait être  /
26 = #include "../ui/dynamicelementtextitemeditor.h"

../sources/ui/elementinfowidget.cpp
24  #include "../ui_elementinfowidget.h"

_ devrait être  /
24  #include "../ui/elementinfowidget.h"

haven't heard from you in a while, are you okay?

Could you please create a PR for your additions to the fonts?
Then we could finalize that topic from here.
I have already adjusted the tabs for the licenses locally: All licenses are grouped in one tab and can be selected for viewing via ComboBox.
But that only makes sense to upload once the fonts are available.
And the customized element collection is also waiting to be activated: Only the fonts are missing...

with translator:
The recent change to moving dynamic text with the additional Shift key is definitely an improvement. However, the text now only moves in small steps and no longer in step with the grid. So I've created a small patch here that changes that. Use the Shift key to move in large steps, and Shift + Alt to move in small steps.

Since the file upload doesn't seem to be working, I've uploaded it to my fork:
https://github.com/ChuckNr11/qelectrotech-source-mirror
If you'd like it, I'll make a pull request.

I have a strange phenomenon, that I would like to understand and get rid of...

There is a fresh installed Debian unstable with QET-Sources from github-branch "qt6-cmake".
From commandline everything compiles fine from cmake, qmake and make.

But sometimes it is much more comfortable to use an IDE to edit sourcefiles and start compilation by clicking a button.

So I installed Qt Creator 15.0.1 based on Qt 6.7.2 (GCC 14.2.0, x86_64) on top of it, imported the QET-codestyle-settings and clicked "compile".
And that's where the phenomenon comes to light: It won't compile, because some header-files cannot be found, see also attachment.

To remember: Everything compiles fine from commandline, so all headers are on the system:

$ dpkg -l | grep libkf6 | grep addons-dev
ii  libkf6coreaddons-dev:amd64  6.11.0-1  amd64  KDE Frameworks 6 addons to QtCore - development files
ii  libkf6widgetsaddons-dev     6.11.0-1  amd64  development files for kwidgetsaddons
$

So there is a setting in Qt-Creator that has to be adjusted to be able to compile from IDE, but I don't see it!

Is there someone who can help "cleaning my glasses"???

Bigger grid dots

I have see that my backgroud of the screen is an raster.
I have found the solution for making the dots bigger in the grid raster.

I noticed that my screen background is a grid.
I found the solution to make the dots in the grid larger.

The file Diagram.cpp is located in /qelectrotech-source-mirror/sources/
The file elementview.cpp is located in /qelectrotech-source-mirror/sources/editor

My directory(folder) is different in the patch file

Erik

I've created a fork at https://github.com/elevatormind/qelectr … rce-mirror with a branch "lang_sv" for it. I don't have much experience in code collaboration earlier, just been coding privately for fun from time to time so still trying to get a grasp on forks with github. If this is interesting, do you want me to create a pull request for this, or handle it another way?

Some background on me as I pop up from nowhere, I'm drawing electrical diagrams for a living at a company constructing control cabinets for elevators. I'm using Elprocad at work but in the process of switching to Zuken E3, and have been using EPlan for a couple of years earlier. I've found QET earlier and played around with it as I find it an interesting project, and have considered using it for work, but it's not quite there yet. But that's how I started to see if I could make a translation for it and here we are!

PS. I've done two other branches with small features that may or may not be useful, will push them up for evaluation and try to post something about them here in the forum
PS 2. And one bigger but messy branch getting QET to compile with QT6 / cmake (with QT6 and KF 6.8+ i've managed to make a static compile of QET)

I installed libsqlite3-dev package but am getting this

00:36:05: Running steps for project qelectrotech...
00:36:05: Starting: "/usr/lib/qt5/bin/qmake" /home/andrew/sources/qt/qelectrotech-source-mirror/qelectrotech.pro -spec linux-clang CONFIG+=debug CONFIG+=qml_debug
Cannot read /home/andrew/sources/qt/qelectrotech-source-mirror/SingleApplication/singleapplication.pri: No such file or directory
Project ERROR: sqlite3 development package not found
00:36:05: The process "/usr/lib/qt5/bin/qmake" exited with code 3.
00:36:05: Error while building/deploying project qelectrotech (kit: Desktop)
00:36:05: When executing step "qmake"
00:36:05: Elapsed time: 00:00.

$ dpkg -L libsqlite3-dev
/.
/usr
/usr/include
/usr/include/sqlite3.h
/usr/include/sqlite3ext.h
/usr/lib
/usr/lib/x86_64-linux-gnu
/usr/lib/x86_64-linux-gnu/libsqlite3.a
/usr/lib/x86_64-linux-gnu/pkgconfig
/usr/lib/x86_64-linux-gnu/pkgconfig/sqlite3.pc
/usr/share
/usr/share/doc
/usr/share/doc/libsqlite3-dev
/usr/share/doc/libsqlite3-dev/changelog.Debian.gz
/usr/share/doc/libsqlite3-dev/changelog.gz
/usr/share/doc/libsqlite3-dev/changelog.html.gz
/usr/share/doc/libsqlite3-dev/copyright
/usr/lib/x86_64-linux-gnu/libsqlite3.so

Maybe qt project file just doesn't know to look for libs there? its my 1st time using qt creator

Salut Laurent !

I created a patch to set the config- and data-directories to system-specific values.

diff --git a/sources/dxf/dxftoelmt.cpp b/sources/dxf/dxftoelmt.cpp
index f2dd572d8..85ea2534f 100644
--- a/sources/dxf/dxftoelmt.cpp
+++ b/sources/dxf/dxftoelmt.cpp
@@ -21,7 +21,7 @@
 #include <QFile>
 #include <QProcess>
 #include <QMessageBox>
-#include <QDir>
+#include <QStandardPaths>
 
 /**
  * @brief dxftoElmt
@@ -71,13 +71,7 @@ QByteArray dxfToElmt(const QString &file_path)
 
 QString dxf2ElmtDirPath()
 {
-#if defined(Q_OS_WIN32) || defined(Q_OS_WIN64)
-    return (QDir::homePath() + QStringLiteral("/Application Data/qet/binary"));
-#elif defined(Q_OS_MACOS)
-    return (QDir::homePath() + QStringLiteral("/.qet/binary"));
-#else
-    return (QDir::homePath() + QStringLiteral("/.qet/binary"));
-#endif
+    return QStandardPaths::writableLocation(QStandardPaths::AppDataLocation) + "/binary";
 }
 
 /**
diff --git a/sources/main.cpp b/sources/main.cpp
index ed460609f..5eb7efca3 100644
--- a/sources/main.cpp
+++ b/sources/main.cpp
@@ -112,7 +112,8 @@ void myMessageOutput(QtMsgType type,
         txt+= context.function ? context.function : "";
         txt+=")\n";
     }
-    QFile outFile(QETApp::configDir()
+    QFile outFile(QETApp::dataDir()
+              +"/"
               +QDate::currentDate().toString("yyyyMMdd")
               +".log");
     if(outFile.open(QIODevice::WriteOnly | QIODevice::Append))
@@ -131,7 +132,7 @@ void myMessageOutput(QtMsgType type,
 void delete_old_log_files(int days)
 {
     const QDate today = QDate::currentDate();
-    const QString path = QETApp::configDir() + "/";
+    const QString path = QETApp::dataDir() + "/";
 
     QString filter("%1%1%1%1%1%1%1%1.log"); // pattern
     filter = filter.arg("[0123456789]"); // valid characters
diff --git a/sources/qet_elementscaler/qet_elementscaler.cpp b/sources/qet_elementscaler/qet_elementscaler.cpp
index 930bae333..b7e362d1e 100644
--- a/sources/qet_elementscaler/qet_elementscaler.cpp
+++ b/sources/qet_elementscaler/qet_elementscaler.cpp
@@ -22,7 +22,7 @@
 #include <QProcess>
 #include <QInputDialog>
 #include <QMessageBox>
-#include <QDir>
+#include <QStandardPaths>
 
 /**
  * @brief QET_ElementScaler
@@ -113,13 +113,7 @@ QByteArray ElementScaler(const QString &file_path, QWidget *parent)
 
 QString ElementScalerDirPath()
 {
-#if defined(Q_OS_WIN32) || defined(Q_OS_WIN64)
-    return (QDir::homePath() + QStringLiteral("/Application Data/qet/binary"));
-#elif defined(Q_OS_MACOS)
-    return (QDir::homePath() + QStringLiteral("/.qet/binary"));
-#else
-    return (QDir::homePath() + QStringLiteral("/.qet/binary"));
-#endif
+    return QStandardPaths::writableLocation(QStandardPaths::AppDataLocation) + "/binary";
 }
 
 /**
diff --git a/sources/qetapp.cpp b/sources/qetapp.cpp
index f1211bb47..e7611fd88 100644
--- a/sources/qetapp.cpp
+++ b/sources/qetapp.cpp
@@ -121,7 +121,7 @@ QETApp::QETApp() :
         tr("Chargement... Initialisation du cache des collections d'éléments",
            "splash screen caption"));
     if (!collections_cache_) {
-    QString cache_path = QETApp::configDir() + "/elements_cache.sqlite";
+    QString cache_path = QETApp::dataDir() + "/elements_cache.sqlite";
 
         collections_cache_ = new ElementsCollectionCache(cache_path, this);
         collections_cache_->setLocale(langFromSetting());
@@ -620,7 +620,7 @@ QString QETApp::customElementsDir()
             }
         }
 
-        m_custom_element_dir = configDir() + "elements/";
+        m_custom_element_dir = dataDir() + "/elements/";
         return m_custom_element_dir;
     }
 }
@@ -657,7 +657,7 @@ QString QETApp::companyElementsDir()
             }
         }
 
-        m_company_element_dir = configDir() + "elements-company/";
+        m_company_element_dir = dataDir() + "/elements-company/";
         return m_company_element_dir;
     }
 }
@@ -780,7 +780,7 @@ QString QETApp::companyTitleBlockTemplatesDir()
         return m_user_company_tbt_dir;
     }
 
-    return(configDir() + "titleblocks-company/");
+    return(dataDir() + "/titleblocks-company/");
 }
 
 /**
@@ -813,7 +813,7 @@ QString QETApp::customTitleBlockTemplatesDir()
         return m_user_custom_tbt_dir;
     }
 
-    return(configDir() + "titleblocks/");
+    return(dataDir() + "/titleblocks/");
 }
 
 /**
@@ -841,21 +841,31 @@ QString QETApp::configDir()
 #ifdef QET_ALLOW_OVERRIDE_CD_OPTION
     if (config_dir != QString()) return(config_dir);
 #endif
-#ifdef Q_OS_WIN32
-    // recupere l'emplacement du dossier Application Data
-    // char *app_data_env = getenv("APPDATA");
-    // QString app_data_str(app_data_env);
-    QProcess * process = new QProcess();
-    QString app_data_str = (process->processEnvironment()).value("APPDATA");
-    // delete app_data_env;
-    delete process;
-    if (app_data_str.isEmpty()) {
-        app_data_str = QDir::homePath() + "/Application Data";
-    }
-    return(app_data_str + "/qet/");
-#else
-    return(QDir::homePath() + "/.qet/");
-#endif
+    QString configdir = QStandardPaths::writableLocation(QStandardPaths::AppConfigLocation);
+    if (configdir.endsWith('/')) {
+        configdir.remove(configdir.length()-1, 1);
+    }
+    return configdir;
+}
+
+/**
+    @brief QETApp::dataDir
+    Return the QET data folder, i.e. the path to the folder in which
+    QET will find user-collections and user-titleblocks by default
+    specific to the current user. This directory is generally
+    C:/Users/<USER>/AppData/Roaming/<APPNAME>
+    on Windows and
+    ~/.local/share/<APPNAME>
+    under UNIX-like systems.
+    \~ @return The path of the QElectroTech data-folder
+*/
+QString QETApp::dataDir()
+{
+    QString datadir = QStandardPaths::writableLocation(QStandardPaths::AppDataLocation);
+    if (datadir.endsWith('/')) {
+        datadir.remove(datadir.length()-1, 1);
+    }
+    return datadir;
 }
 
 /**
@@ -1536,7 +1546,7 @@ void QETApp::useSystemPalette(bool use) {
                 "}"
                 );
     } else {
-        QFile file(configDir() + "style.css");
+        QFile file(configDir() + "/style.css");
         file.open(QFile::ReadOnly);
         QString styleSheet = QLatin1String(file.readAll());
         qApp->setStyleSheet(styleSheet);
diff --git a/sources/qetapp.h b/sources/qetapp.h
index 2f4cdc402..572e2c837 100644
--- a/sources/qetapp.h
+++ b/sources/qetapp.h
@@ -97,6 +97,7 @@ class QETApp : public QObject
         static QETProject *project(const uint &);
         static int projectId(const QETProject *);
         static QString configDir();
+        static QString dataDir();
         static QString languagesPath();
         static QString realPath(const QString &);
         static QString symbolicPath(const QString &);
diff --git a/sources/ui/aboutqetdialog.cpp b/sources/ui/aboutqetdialog.cpp
index b1dc0abc0..f94b62449 100644
--- a/sources/ui/aboutqetdialog.cpp
+++ b/sources/ui/aboutqetdialog.cpp
@@ -208,7 +208,7 @@ void AboutQETDialog::setLicence()
 */
 void AboutQETDialog::setLoginfo()
 {
-    const QString path = QETApp::configDir() + "/";
+    const QString path = QETApp::dataDir() + "/";
     QString filter("%1%1%1%1%1%1%1%1.log"); // pattern
     filter = filter.arg("[0123456789]"); // valid characters
     Q_FOREACH (auto fileInfo,

As already said in previous post the general configuration-file of QET and the stalefiles are completely managed by Qt-Library-functions. So they are already at system-specific locations. There is no need to touch them with these modifications!

I uploaded that patch to my fork of QET at https://github.com/plc-user/qelectrotech-source-mirror and can create a pull-request, if you wish, Laurent.

@all:
Everyone who can compile QET from sources is invited to download, compile and test the software! 
But be aware:
The location of configurations, the elements-collections and the titleblocks may (will) have changed!
Please give feedback here or at github about your experience!

Thanks in advance!
  plc-user

For translation from youtube
I use in firefox : Download Youtube Subtitles

Youtube
Jenny lectures : https://www.youtube.com/@JennyslecturesCSIT/playlists

And with QT
https://www.youtube.com/@VoidRealms/playlists

Erik

This is my first post after just joining this discussion, so please forgive me and provide kind assistance if I have posted to the wrong subsection.

I am new here but a real enthusiast and loving this community so far. I have a background in coding and in technology and feel I could help with documentation, at least for starters.

As a new member in this forum and wish to share and gain some knowledge. I am looking forward to create my own discussion to resolve my query and gain some knowledge though I have taken part in various discussion which is definitely helped me a lot.

Also in what category should be taken depends on what factors?

Thank you in advance.