You are not logged in. Please login or register.
QElectroTech → Posts by scorpio810
Hallo plc-user hello vadoola,
thanks for --release arguments I don't remember it.
Source code for launch dxf2elmt:
https://github.com/search?q=repo%3Aqele … ;type=code
@vadoola: FYI a little video howto use previous dxf2elmt in GUI QET element editor.
Regards,
Laurent
git clone https://github.com/Vadoola/dxf2elmt.git dxf2elmt_vadoola
cd dxf2elmt_vadoola
rustup update
cargo buildProgram work well in a terminal with CLI, not when I put the binary dxf2elmt in ~.qet/binary/ and I use QET element editor
menu Import DXF, not stdout?
ps: size of the binary is very big after cargo build... ~57,6 Mio (60414840) (debug?)
Is it possible to add an argument to your program for instead of write in a .elmt file, return the xml (string) in the stdout ?
If yes, I can use your program trought qelectrotech to import a dxf directly inside the element editor ? You will make a lot of happy user
Hello vadoola and welcome.
No activity of Antionio since November 8, 2023 : https://github.com/antonioaja
I hope he's all right ....
Or see online element viewer https://download.qelectrotech.org/qet/e … index.html
Ca fonctionne pour les numéros de fils avec reset par folio.
Malheureusement, quand tu quittes le folio et que tu reviens dessus pour ajouter un fil supplémentaire, QET ne retient pas où il était arrivé et recommence à numéroter à partir de 1.
Oui, c'est le bug remonté sur l'autre post... en principe il est rare de rajouter des conducteurs dans un folio qui a déja été dessiné ...
Par contre ça fonctionne bien pour les éléments.
Si quelqu'un peut se pencher sur les fichiers de code que j'ai mis en lien?Tout comme moi ou Joshua nous n'avons plus le temps depuis plusieurs mois.
Bonjour,
voir ce sujet pour la numérotation et ses problemes:
https://qelectrotech.org/forum/viewtopic.php?id=2799
La fonction câbles n'a pas encore été codé, mais quelques astuces:
https://qelectrotech.org/forum/viewtopi … 157#p17157
Cordialement,
Laurent
I saw the "Apply properties to all conductors of this potential" flag but if I uncheck it, change the properties and enter it again it is enabled again (tried with 0.100.0-dev and 0.90).
It's deliberate!
Its for safety reasons, For security reasons, you should deactivate this checkbox each time you modify conductors. For example, adding a new wire with a different section in the equipotential wires..
Edit:
ps : I hope we've answered your question, which isn't easy to explain why we've put this in the code. I also hope we haven't offended you or questioned your skills as an electrician, that wasn't the point, if it was I apologise in advance.
Best regards,
Laurent
In your example .qet you shared, you wrote this:
If I set the properties of this wire they
are also assigned to the other one.
In practice they are two different wires
that start from the same terminal.
One wire must be 25mmq and the
other 1.5mmq.
It's forbidden and dangerous to do so, and I wouldn't advise it. You should always connect two wires of the same section to the same screw terminal.
Only when you connect a 1.5mn² wire, for example, to a large busbar or repartitor but of course your wire is protected downstream by a 10A fuse will you have to cheat with a non-terminal type symbol to connect them together.
So you have to use something other than the terminal or report folio to connect them like a fuse and cut equipotential, otherwise equipotentiality would be the same and section applied to all equipotential conductors, yes I know that changing the section or others entities of a conductor breaks equipotentiality...on QET program!
Of course isn't perfect but is it for safety reasons!, like say plc-user
Side Note: I use Sonoma, maybe....
You don't have this issue?
Same like you,Sonoma too, and I don't have this issue... strange!
https://qelectrotech.org/forum/viewtopi … 829#p18829
FYI I compile QET_elementScaler under windows 10 VM based on C.Gilles DigiKam bundle VCPKG https://invent.kde.org/graphics/digikam … type=heads
Work fine.
ps: I've tried other Windows compilations than the usual MXE cross-compilation, so here it's not static but in shared mode with *dll files.
https://download.qelectrotech.org/qet/b … Scaler.zip
~/win_share/QET_elementScaler$ tree
.
├── libgcc_s_seh-1.dll
├── libstdc++-6.dll
├── libwinpthread-1.dll
└── QET_ElementScaler.exe
1 directory, 4 fileshttps://www.virustotal.com/gui/file/9d1 … ?nocache=1
Hallo plc-user,
thanks for quick-guide.
I prefer to do as explained above, it's much quicker, I think
Personally, here's how I do it with the little time I've spent on it:
I click on the element I want to convert, then I enter to the element editor, I press crtl + a and delete all parts, because at the moment the external plugin only opens an elm file, not the element in focus in the editor, otherwise we'll have two elements on top of each other.
Then I import an element to resize/flip mirror with file dialog, I look for where it is in the qet user folders and I choose my options. If I'm not happy, I just do an undo or click on the refresh icon. And re try it...
After off course you can use it on the terminal for batch lot see the QET_elementScaler readme file and use convert scripts and adapt these.
Done for osx arm64 QET build and QET_ElementScaler arm64 OSX binary, tried it run ok.
Ok, so I can revert this commit https://github.com/qelectrotech/qelectr … b7361ad4b6
Does it work for macOS ( intel or arm )?
Yes it tried it when I build intel OSX bundle and provide by the same the x86_64 osx binary, not time today to build osx arm64 builds.
On macOS the problem with the dialog box to open elmt to resize does not display hidden files like the .qet/ directory by default, Yes I know a workaround exists but I forgot...
Hello Robert,
you are welcome.
Maybe you could help Integrated-Circuit see https://qelectrotech.org/forum/viewtopic.php?id=2770
and https://github.com/qelectrotech/qelectrotech-doc/pull/3
Best regards,
Laurent
OK, so can I come back to this commit if the previous OSX arm64 application has already worked for you?
Did the previous version work for you? Maybe this issue comes from this commit?
https://github.com/qelectrotech/qelectr … b7361ad4b6
Hallo plc-user,
done and rename w64/w32 exe name see why https://github.com/qelectrotech/qelectr … r.cpp#L122
Regards,
Laurent
Maintenant qu'on sait que ces deux dossiers y sont, peux tu reproduire le bug?
QElectroTech → Posts by scorpio810
Powered by PunBB, supported by Informer Technologies, Inc.
Generated in 0.162 seconds (15% PHP - 85% DB) with 6 queries