1 Reply by elevatormind

(36 replies, posted in FR : Aide, suggestions, discussions, ...)

@plc-user
In my "liberation-fonts" branch, the liberation fonts is directly usable in QET (on all OS, without any extra action needed), but it is not supplied to the OS. But is that really necessary if that is what you mean? I haven't looked at it, but the font should be able to be embedded when you export to PDF for example.
It should definitely be the default font in QET as you say though, otherwise people will probably not use it.

The osi-font could be supplied as well, for those who like it nomicons/smile I've actually tried it but personally don't like it and think "regular" fonts look better, but I can imagine there might be some customer somewhere demanding it. It will still be your own choice to use it, so it wouldn't hurt to supply it as well

Go to forum: FR : Aide, suggestions, discussions, ...

2 Reply by elevatormind

(36 replies, posted in FR : Aide, suggestions, discussions, ...)

The Liberation fonts would be excellent! I am 99% sure they shouldn't be any problem to use, only thing we would need to add is Copyright notice and the License for them in the "About"-box.

The OFL-license seems common for open source fonts:
https://openfontlicense.org/how-to-use-ofl-fonts/

I also think one sans, one serif and one monospace font should be enough. It's not Adobe Illustrator we're working on here nomicons/smile

Edit:
https://github.com/elevatormind/qelectr … tion-fonts

Go to forum: FR : Aide, suggestions, discussions, ...

3 Reply by elevatormind

(3 replies, posted in EN : Help, suggestions, discussions, ...)

I just added a PR related to this. It will show "<Shift> to move" in the mouse hover text for the texts of an element.

https://github.com/qelectrotech/qelectr … r/pull/386

Go to forum: EN : Help, suggestions, discussions, ...

4 Reply by elevatormind

(36 replies, posted in FR : Aide, suggestions, discussions, ...)

@plc-user:
Maybe we can pick one or a couple of standard open-source font(s) and bundle it as a Qt resource? It would be usable on all OS then.

Peut-être pourrions-nous choisir une ou deux polices open-source standard et les regrouper en tant que ressource Qt ? Elle serait alors utilisable sur tous les systèmes d'exploitation.

Go to forum: FR : Aide, suggestions, discussions, ...

5 Reply by elevatormind

(117 replies, posted in Code)

I don't know about that nomicons/smile VS code + GitHub copilot addon makes wonders, it's almost scary how the AI can predict with auto-complete what I wanna do and explain code I don't understand, and it knows Qt to 100%... All the comments/doxygen-comments in AutoSaveFile probably were made to 90% by GitHub copilot also. It's extremely useful when used right, but don't expect it to write all code for you.

I'll try to fix the AutoSaveFile issue I know about this weekend. And please do continue to contribute and help on both master and qt6-cmake! The qt6-cmake branch definitely needs a lot of testing! Regarding the SingleApplication problem, it might be some combination of Qt 6.6+ with AutoSaveFile. Don't remember if I had the same problem with the KCoreAddons, but it's possible it only showed up after I created AutoSaveFile as a replacement.

The SingleApplication problem with QT 6.6+ seems to be acknowledged here though:
https://github.com/itay-grudev/SingleAp … issues/190

Go to forum: Code

6 Reply by elevatormind

(117 replies, posted in Code)

I didn't see your last post plc-user before posting.
The problem with SingleApplication I can confirm, but I don't get the problem when compiling with Qt 6.5.3 (but with 6.8.2 runtime). I think I read somewhere on the SingleApplicaton project that Qt drastically changed the way QSharedMemory works in Qt 6.6+, and that's the (probable) cause of this problem. Which version of Qt are you compiling against?

There is also another problem with AutoSaveFile at the moment. If you have a file open, terminate QET, rename or move your project file, start QET again, QET will crash trying to recover the now missing project file.

Edit:
Removing stale shared memory files in /dev/shm makes QET start again.

Go to forum: Code

7 Reply by elevatormind

(117 replies, posted in Code)

You're fast plc-user, i've just uploaded and you've already tested it nomicons/smile

I can't object to directory name in lower-case for consistency, and managing the autosave-directory in qetapp.* makes sense too. I'll write those changes.

Note that  KWidgetAddons and KCoreAddons are not needed on my qt6-cmake branch now!
Another request for you plc-user (and everybody else really), do all qt6 work on qt6-cmake branch for now. I did a rebase on the qt6-cmake branch against the master branch yesterday, and there were three commits that caused merge conflicts. Those commits were similar to https://github.com/qelectrotech/qelectr … 7121e1f85b, and then some similar changes made to the qt6-cmake branch. Keeping the qt5/qt6 version checks intact on the master branch makes it a lot easier to keep the qt6-cmake branch updated with other changes to the master branch. But I would like Laurent's input on this, he has the last say on how we should be going forward with the qt6-cmake branch.

On another note, i've noticed an issue with SingleApplication and Qt > 6.5. If QET terminates prematurely, the shared memory file doesn't clean up and stops you from starting QET again as it thinks it's a second QET-application starting... I've noticed development of SingleApplication is active but slow, I might have to work on some temporary replacement there too nomicons/smile SingleApplication should be used if it's fixed though, it's a solid project and we don't want to reinvent the wheel.

Go to forum: Code

8 Reply by elevatormind

(8 replies, posted in Code)

Very nice! I'll try to work on a replacement for KAutoSaveFile when time allows, hopefully it will make it easier to continue develop QET. I don't use Qt Creator myself, but it's probably an easier way to get into development of QET. So if it helps with Qt Creator I'll definitely try to do it!

I just can't understand why those classes, especially the color button / combo box, are not implemented in Qt itself.

Go to forum: Code

9 Reply by elevatormind

(8 replies, posted in Code)

Hello plc-user and Laurent, I think the KF6-addons mostly create problems with compiling (and maybe packaging?).

I just created a pull request to qt6-cmake with new minimal classes to replace KColorButton and KColorCombo from KWidgetsAddons. Compiles and runs fine here without the use of KWidgetsAddons, feel free to try it out.

If there is interest for it, I can look at replacing KAutoSaveFile from KCoreAddons (when time allows me) which I believe is the last class used from the KF6 addons.

Go to forum: Code

10 Reply by elevatormind

(117 replies, posted in Code)

I also just noticed these messages when starting Qet:

qt.core.qobject.connect: QObject::connect: No such signal QSignalMapper::mapped(QWidget *) in /home/magnus/qet-src/sources/qetapp.cpp:118
qt.core.qobject.connect: QObject::connect: No such signal QSignalMapper::mapped(QWidget *) in /home/magnus/qet-src/sources/qetdiagrameditor.cpp:98

Go to forum: Code

11 Reply by elevatormind

(9 replies, posted in Code)

Hello plc-user, thanks. If there are other people addressing this problem I'm not completely wrong nomicons/smile this is probably the first thing that annoyed me wit Qet.

What I am wondering is if the shift-button is interfering with something, but I haven't noticed anything. But it could be any button really, and maybe a hint should be implemented in the popup when you hover over the text that tells you that shift or whatever button moves the text.

Go to forum: Code

12 Reply by elevatormind

(117 replies, posted in Code)

Nice, just happy to help. Like I said, did too much work on this to just let it sit on my computer nomicons/smile

I attached a screenshot of the table issue, you can see how wide it is. And it grows in width each time you refresh the table.

I've only gotten it to compile with the Qt6 Online installer, i'm on Ubuntu 22.0. Latest Qt6 I see as a package now is 6.4.2, and I think it was 6.3 something when I tried to compile and started to make it work with qt6. So it's definitely possible it works with earlier versions than 6.8, 6.7 obviously works nomicons/smile
Also the KF6-versions are old on my Ubuntu release so I think I was only able make KF6.8 compile reliably from source.

Go to forum: Code

13 Reply by elevatormind

(9 replies, posted in Code)

...and thanks for adding the translation!

uploaded my other branches, see my post in the Qt6-thread.
I've played around with 'git rebase' too much I see though, the other branches are merged into qt6-cmake. Need to read up a bit on git nomicons/smile

it's supposed to be two other separate branches:
conductor_texts, adding variables %wf, %wv, %wc and %ws to conductor labels
selective_move, need to hold down shift to move dynamic texts of a symbol - otherwise the whole symbol is moved. (I find it very annoying to move symbols sometimes, the texts are always moved when I want to move the symbol instead)

I have a local backup copy of my repository, I'm gonna see if I can rescue the commit history and branches.

Go to forum: Code

14 Reply by elevatormind

(117 replies, posted in Code)

hello, I just uploaded my qt6-cmake branch which I have succesfully compiled QET with QT 6.8.

github.com/elevatormind/qelectrotech-source-mirror/tree/qt6-cmake

My steps to succesfully compile QET:

Install Qt 6.8.0 (I installed it with the online installer), assuming Qt 6.8.0 installed to "~/Qt/6.8.0/"

Install ECM 6.8.0 manually:

git clone [url]https://github.com/KDE/extra-cmake-modules.git[/url] ecm-src
git checkout tags/v6.8.0
mkdir ecm-build && cd ecm-build
~/Qt/6.8.0/gcc_64/bin/qt-cmake -DBUILD_TESTING=OFF -DBUILD_SHARED_LIBS=OFF -DCMAKE_BUILD_TYPE=<Release or Debug> -G Ninja ../ecm-src
cmake --build . -j<n>
sudo cmake --install .

Compile QET (from a clean build-dir):

~/Qt/6.8.0/gcc_64/bin/qt-cmake -DBUILD_TESTING=OFF -DBUILD_SHARED_LIBS=OFF -DCMAKE_BUILD_TYPE=<Release or Debug> -DPACKAGE_TESTS=OFF -DBUILD_KF6=ON -G Ninja ../qet-src
cmake --build . -j<n>
sudo cmake --install .

Note, this will download and compile KCoreAddons and KWidgetAddons from github with cmake by default so no need to have them installed. This is controlled by the BUILD_KF6 (ON by default) and KF6_GIT_TAG (6.8.0 by default) cmake options.
I haven't got ExtraCmakeModules to work with the download and compile with cmake, but I assume it's only used for compiling and not needed at runtime so shouldn't be an issue.

I can't remember exactly why but there were some problems compiling KF6 addons lower than 6.8.0.

There are a lot of compile warning and error fixes, these maybe should be reviewed as I can't guarantee any bugs or side effects, there are probably some other fixes in there also that might not be related to Qt6. I remember putting all the .qm-files in a Qt-resource for example.

I have so far discovered two issues with QET/QT6.
1. Symbol library panel, the texts don't show until you hover over them with the mouse.
2. Nomenclature tables are growing in width, when you reload them the width increases.

Go to forum: Code

15 Reply by elevatormind

(9 replies, posted in Code)

Hello again, sorry for late reply. I have a lot going in my private life so i will probably be a bit inactive and not always reply very fast, but I will try to contribute now and then.
I will upload everything to my github repository

Go to forum: Code

16 Topic by elevatormind

(9 replies, posted in Code)

Hello QElectroTech team, I've been working on a Swedish translation for some time but never gotten around to actually share it until now.

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)

Go to forum: Code