Search options (Page 1 of 3)

Yeah, I never updated this forum post, but I probably should have. I got this resolved and released 0.5.0 about 2 months after that last comment with support for nested blocks and whole bunch of other changes.

The newest release is 0.5.1 (minor bug fix release), and I actually have some other changes that I've been meaning to finish testing and release. I was hoping to do it over the holidays while I was visiting family, but my laptop died a few days before I left..

if you grab the latest version and you are still having issues, please let me know, I'll try and get it fixed.

Thanks this gives me a place to start looking.

I'll give it a go. While I'm not a fan of Windows, unfortunately my work laptop is running Windows 11. While I haven't done any in a while, I do have it set up for Qt development, so hopefully it won't be too much trouble to get it compiling.

I'm certainly not a git expert either, but I'll start by trying to get the existing qt6-cmake branch compiling, and then see what I can do from there.

Appreciate the help, hopefully I can get something useful going.

Hi joao.silveira

I don't have a tutorial specifically but I can try and walk you through some steps quickly
- Launch QElectrotech
- Under Collections->User Collection (typically on the right hand side of the QET Window) right click on User Collection
- Click "New Element" in the pop up menu
- Select the folder you wan to put it in and click "Next"
- give it a file name, and click "Next"
- give it an element name, and click "Finish"

This will launch the Element Editor. From the Element Editor Window follow the below steps
- File->Import a dxf
- If you don't have the dxf2elmt software placed in the correct folder, it will open a popup window saying it can't find it. There will be a download button, which you should probably ignore, and a button to open the installation folder. Click that and drop a copy of dxf2elmt in that folder (there are Windows and Debian versions you can download from https://github.com/Vadoola/dxf2elmt/releases, and scorpio810 has attached some MacOS versions up a few comments in this thread).

Once you have the dxf2elmt program installed in the correct folder:
- go to File->Import a dxf
- In the popup select the dxf file and click ok.

That should pretty much be it, but you will need to add terminals and such yourself to connect wires to them in QElectrotech.

The dxf2elmt program specifically converts DXF files, NOT DWG files. If you only have a DWG file you would need to convert it to a DXF first, there are some various programs available to do this, LibreCAD and QCad should be able to, I believe FreeCAD as well, but have less experience with it.

Hopefully this helps.

English

As the maintainer of dxf2elmt, I would also ask what issue did you find getting the dxf to load? Was it installing the dxf2elmt plugin? Was the plugin failing to convert anything?

If the problem is with dxf2elmt itself, and you can link me to the dxf files you were using, I'll take a look and see what might have been going wrong.

Machine Translated - Traduction automatique
En tant que mainteneur de dxf2elmt, je voudrais également savoir quel problème avez-vous rencontré lors du chargement du fichier DXF ? Était-ce l'installation du plugin dxf2elmt ? Le plugin n'a-t-il pas réussi à convertir quoi que ce soit ?

Si le problème vient de dxf2elmt lui-même, et que vous pouvez me donner le lien vers les fichiers DXF que vous utilisiez, je vérifierai ce qui a pu poser problème.

Are you only getting that on the Mac? Or on other machines too? It's interesting that it's only happening when being called from QET and not from the CLI.

Either way I see what the issue was. I finally added a bit of logging trying to troubleshoot some issues with the nested blocks. A bit of poor error handling on setting up the logging slipped through to the release....ah actually I think it makes sense now depending on exactly how you are running it. By default it just creates a dxf2elmt.log file in the same folder as the exe. If you have write permissions on the folder when running it from the CLI, no problem. If it doesn't have write permissions for the folder where the plugin is run from it will probably get that ReadOnlyFilesystem error, and then the poor error handling for the logging file is causing it to panic and halt execution. I'll see if I can get a bug fix release out shortly.

Do you know what the typical logging system on MacOS is? On Linux of course you have syslog, or the systemd journal. Windows you could use the Event System....The last Mac I used consistently was PowerPC based, so I don't really know the system well now. Trying to figure out what options I have for logging other than just creating a log file.

Salut Laurent, Hallo plc-user,

I know it's been a while since I've been around. I hope everyone is doing well. I've had a lot going on, as well as a few injuries unfortunately that slowed down development for a bit.

There could be some other issues with it still, but I'm pretty happy with the nested block support as it stands currently. As there were a fair number of changes for this support, plus other things that have changes since the last release was cut, I decided it was worth marking as a new release. So version 0.5.0 was released about an hour ago.

Let me know if you find any specific issues with it.

Wow...2.8MB that's a big dxf, Looks like it has a whole lot of blocks. Should be a good test drawing to find some deficiencies in dxf2elmt hopefully.

Salut Laurent, Hallo plc-user,

And to anyone else willing to help out.

I created a branch to try and finish up on the issues with nested blocks: https://github.com/Vadoola/dxf2elmt/tree/nested_blocks, as originally brought up at https://qelectrotech.org/forum/viewtopic.php?id=2890

While there are still some minor issues (like text positioning but that's not exclusive to blocks), so far in my testing with a few files it seems to be pretty good.

If anyone has some good dxf files with nested blocks they want to test against let me know. I'll try and wrap up some of those minor issues, and merge it back into the main branch soon.

Salut Laurent, Hallo plc-user

Since it's unlikely that Antonioaja will be working on dxf2elmt going forward and and my fork has diverged quite a bit at this point, I was considering on disconnecting my fork from his. I still plan on giving him full credit for the work he did, and will update the Readme to link back to his repo, I just wanted to separate the fork.

There are some things I need to consider, I thought I saw somewhere that it might ruin any issues you have, but I'm not sure. Either way in order to separate it from Antonio's fork my repo can't have any fork's itself. Would you two be willing to delete the forks you have made from my repo so I can separate it from Antonio's? Then you can refork it if you need to.

Hello everyone,

A few months ago when I was looking to improve the font handling in dxf2elmt, I was trying to figure out what the font info string in the XML file is. I noticed it was using a built in method on QFontInfo that writes it out to a string, and I had to go dig into the Qt Source code to figure it out, as it appears to be undocumented.

I bring this up because back when I was researching this I came across this bug in Wireshark, that says the FontInfo string is not backwards compatible between Qt5 and Qt6: https://gitlab.com/wireshark/wireshark/-/issues/18553.

I forgot about it until just now when discussing a pull request plc-user made for dxf2elmt about text positioning. I just wanted to bring this to your attention since you guys are working on compiling it with Qt6, it's possible something will need to be done to make sure the font info from elemt files created with a Qt5 version works correctly with a version compiled with Qt6.

So I did a quick look, I never quite finished the logic for nested blocks, so that is the problem here. I'll add it to the to do list. Thank you.