Salut qmcc,
wahrscheinlich nicht die erhoffte Antwort zu Deiner Frage, aber etwas zum Lesen:
https://qelectrotech.org/forum/viewtopi … 694#p19694
You are not logged in. Please login or register.
QElectroTech → Posts by plc-user
Salut qmcc,
wahrscheinlich nicht die erhoffte Antwort zu Deiner Frage, aber etwas zum Lesen:
https://qelectrotech.org/forum/viewtopi … 694#p19694
Hello Andy.nx,
I'm just curious:
Why do you need the proprietary format "dxf" if it doesn't seem to matter which software you can open it with?
Then perhaps free formats (SVG) that can be further processed with free software (Inkscape) could also be considered?
Tried with current version QET 0.10dev:
A dxf-file is created what LibreCAD can open and it looks quite o.k.
Maybe this helps:
In Element-Editor you can set the property "Width" for dynamic_text.
Then the text is automatically wrapped at spaces.
You can also set the Property "Width" afterwards in design-editor.
I downloaded 0.100-dev and finally I made it work without installation (7zip works fine but windows file administrator fails unzipping all the element nested folders).
Maybe the same "problem" from here?
https://qelectrotech.org/forum/viewtopi … 755#p19755
And:
It's always a good idea, NOT to copy the Ready-To-Use - version to c:\programfiles
try to use something like c:\tools\qet or so...
Hello everybody!
In Element-Editor the Edit-Fields (SpinBoxes) for X- and Y-Position of terminals lose focus every time a key on the keyboard is hit. That makes editing the position with keyboard very annoying!
Trying to fix that, I edited the QET-Sources a bit and now I need someone to check, whether there are any side-effects.
For me it seems to work, but my Qt-Knowledge is very restricted, so I don't know if there may be something wrong.
Actually it compiles without warning!
Here's what I changed:
diff --git a/sources/editor/ui/terminaleditor.cpp b/sources/editor/ui/terminaleditor.cpp
index c84ae5ecf..77e0c2112 100644
--- a/sources/editor/ui/terminaleditor.cpp
+++ b/sources/editor/ui/terminaleditor.cpp
@@ -219,9 +219,9 @@ void TerminalEditor::activeConnections(bool active)
{
if (active) {
m_editor_connections << connect(ui->m_x_dsb, QOverload<qreal>::of(&QDoubleSpinBox::valueChanged),
- this, &TerminalEditor::posEdited);
+ [this]() { TerminalEditor::posEdited(); ui->m_x_dsb->setFocus();} ) ;
m_editor_connections << connect(ui->m_y_dsb, QOverload<qreal>::of(&QDoubleSpinBox::valueChanged),
- this, &TerminalEditor::posEdited);
+ [this]() { TerminalEditor::posEdited(); ui->m_y_dsb->setFocus(); } ) ;
m_editor_connections << connect(ui->m_orientation_cb, QOverload<int>::of(&QComboBox::activated),
this, &TerminalEditor::orientationEdited);
m_editor_connections << connect(ui->m_name_le, &QLineEdit::editingFinished,
Could someone please use this diff to check, if it's ok?
Maybe you, Laurent?
In case that code works without side-effects I would create a pull-request on GitHub.
Thanks in advance!
plc-user
Question:
How can we help if we don't know what's going wrong? No Sample-Files, no screenshots ... nothing!
It's not helpful for potential helpers if someone else writes that he/she has the same problem!
So:
What is going wrong and where?
Maybe this post can help:
https://qelectrotech.org/forum/viewtopi … 901#p19901
Hello samuelps.hr,
as Laurent already said:
First you need to download the whole sourcecode-package from github
https://github.com/qelectrotech/qelectr … rce-mirror
and unpack to a local directory.
With Qt-Linguist you open one or more ts-files from that directoy-structure.
My suggestion: qet_pt, qet_pt_BR and qet_en
Then you can compare the translations.
When you look at the columns on the left and push the mouse-cursor over the symbols, you can see the "completion-status" for that translation. As you can see: There are many question-marks for Portuguese. In the screenshot you see that there is a translation for Portuguese, but the translator wasn't sure, if this translation is correct. When you say it's correct, set the status to "done", otherwise correct the phrase and then mark as done.
When finished you can "release" the language-files and publish them here (qet_pt.ts and qet_pt.qm) as ZIP or create a pull-request at github, if you have an account. But I guess Laurent would be happy to upload the files to github, if you post them here...!
Best regards
plc-user
Hello samuelps.hr
Looking at the language-files:
There are many translations missing or still declared "unfinished" (1921) for Portuguese!
There are even more translations for Brazilian Portuguese finished: only 51 declared "unfinished".
Maybe this is a good start for you to help the other Portuguese QET users and complete the Portuguese translations?
EDIT:
scorpio810 wrote a little manual:
https://qelectrotech.org/forum/viewtopi … 375#p13375
Best regards
plc-user
Can you give a simple example of your art here so that others can benefit from it?
Thanks in advance!
By default, the slave elements do not have their own labelling as they are usually an integral part of the master element (relay contact etc.). I therefore assume that this is probably not possible at the moment.
A similar request came up some time ago: switches with knobs, push rods, etc., which must appear somewhere in the parts list, too.
Please read edited part (second half) from here:
https://qelectrotech.org/forum/viewtopi … 897#p19897
Es wäre schön, wenn der Ersteller hier einen Hinweis auf den anderen Thread geben würde, in dem er dieselbe Frage noch einmal gestellt hat und Hinweise für die Abhilfe seines Problems bekommen hat!
Danke!
Does anybody know, if jubert.loic is still alive?
He did not answer, if the suggestion helped, nor did he say "thanks" for the help!
Did you use Forum-Search?
This is asked frequently...
Pull the new/reworked element on any folio of your project.
QET asks, if you want to keep both versions or replace any occurence by the new one.
(you don't have to place the new element!)
Close the project and re-open: voilá!
Connections will be kept, if the terminals are at the same positions as before!
What is wrong with the created element?
Open the element-file with Element-editor, delete the "garbage" and save the element again.
When you then use QET_ElementScaler with a factor of 97 you'll get something like the attached file with a perfect scale of 1mm = 2px!
BUT:
For such a relatively simple part, I wouldn't do the work with dwg to dxf to elmt with all the imponderables and the resulting huge files! You'll have to edit these parts with Element-Editor anyway!
When I look at the real part, there are a handful of rectangles and circles that can be put together quite quickly with the element editor. Then you are also flexible if, for example, you want to have the entire series from the manufacturer as front view in QET.
In my opinion, a few rectangles and circles are enough for circuit diagram symbols anyway (see manufacturer parts Wago or Weidmüller).
[EDIT]:
In my opinion dxf2elmt produces "better" elements:
https://github.com/antonioaja/dxf2elmt/releases
[EDIT 2]:
LibreCAD can handle the dwg from your first post and can export dxf that can be read by dxf2elmt.
https://github.com/LibreCAD/LibreCAD/releases
What tool did you use to convert what format to which one?
What error-messages do you get from the converter(s)?
Here https://gprivate.com/6b88g you find an online-converter where you can set different dxf-versions as output-format.
Btw, this topic is not about positioning (...)
Do I really have to tell you what you wrote?
Btw. any text position (not only in symbol) should respect text align setting. But this is not good implemented.
[EDIT]:
I am also a user of QET and do not want to discourage you from continuing to work with QET or even discourage you from donating to the project!
However, if you had followed the discussions here over the last few weeks and months, you would have realised that we currently have a shortage of active developers.
(Good) ideas are regularly posted here, but there is a lack of people to realise them.
I don't want to discuss that there are (many?) things that may be better implemented in QET:
Even the Main-Developer says so!
Maybe this helps to explain text-positions:
https://qelectrotech.org/forum/viewtopi … 867#p19867
Es sollte einen Versuch wert sein, dich (ausgehend von Version 0.6) Stück für Stück zu neueren Versionen vor zu arbeiten:
Wenn die Versionssprünge zwischen deinen Versuchen klein sind, sollte es doch funktionieren, dich bis zur aktuellen 0.10 durchzukämpfen. Auch die älteren QET-Versionen liegen im Download-Bereich als "Ready-to-use" vor, sodass du die Pakete nur auspacken musst. Die Ready-to-use können auch alle gleichzeitig auf dem Computer liegen. Dann kannst du zwischen den Versionen wechseln...
Ein Versuch kann nicht schaden. Es sei denn, du hast von deinem Projekt keine Sicherungskopie gemacht...
Salut Laurent!
(...) But I think the source of problem is on QET code for copy and paste elements parts and don't change UUID ..
You said it: The element editor!
As another user in the forum has also noted, copy-and-paste is worthy of revision anyway: The insertion position depends on what was copied in the selection and in my opinion this is not comprehensible. This also leads to the "problem" that graphic parts may be inserted at positions that have 5-6 decimal places, which cannot be corrected with the element editor alone, or only with difficulty.
A possible variant would perhaps be to round the position to the smallest possible shift difference when shifting graphic parts. Example: A graphic part can be moved by 0.1 px using the Ctrl key with Cursor-Keys. The position could then be rounded to 0.1 px.
However, this task is " slightly" beyond my Qt programming knowledge for now ...
Back to the initial question:
Will take care of the elements in the next few days!
Best regards
plc-user
Eine Frage an die Entwickler:
In der Element-Sammlung befinden sich über 500 Elemente, bei denen die dynamischen Texte oder die Anschlüsse UUIDs haben, die in derselben Datei mehrfach vorkommen. Sollen wir die Dateien korrigieren? Ich hätte dafür etwas vorbereitet...
via Online-Translator:
A question to the developers:
There are over 500 elements in the element collection where the dynamic texts or the terminals have UUIDs that appear multiple times in the same file. Should we correct the files? I would have prepared something for this...
via Online-Translator:
Une question aux développeurs :
Dans la collection d'éléments, il y a plus de 500 éléments dont les textes dynamiques ou les connecteurs ont des UUID qui apparaissent plusieurs fois dans le même fichier. Faut-il corriger ces fichiers ? J'aurais préparé quelque chose pour cela...
Hallo Nikolo!
Wir haben beide profitiert:
Der QET_ElementScaler ist wieder etwas besser geworden, weil er nun mehrfach vorkommende UUIDs erkennt und ersetzt!
Da wir bei diesem Thema lange aneinander vorbeigeredet haben: Bitte beim nächsten Thema deutlicher beschreiben, was du tust bzw. was du vorhast! Danke!
via Online-Translator:
Salut Nikolo !
Nous en avons tous les deux profité :
Le QET_ElementScaler s'est à nouveau un peu amélioré, car il reconnaît et remplace maintenant les UUIDs qui apparaissent plusieurs fois !
Puisque nous nous sommes longtemps ignorés sur ce sujet : Pour le prochain sujet, merci de décrire plus clairement ce que tu fais ou ce que tu as l'intention de faire ! Merci !
Ich glaube, ich weiß nun, was Du meinst!
Die Textausrichtung bezieht sich immer auf den Punkt X/Y, der bei der Erstellung des Elements gewählt wurde. Im Diagramm-Editor kann das nachträglich nur durch Verschieben des Textes erreicht werden: Es reicht nicht, im Diagramm-Editor die Ausrichtung, zu ändern!
via Online-Translator:
Je crois que j'ai compris ce que tu voulais dire !
L'orientation du texte se réfère toujours au point X/Y qui a été choisi lors de la création de l'élément. Dans l'éditeur de diagramme, cela ne peut être obtenu ultérieurement qu'en déplaçant le texte : Il ne suffit pas de modifier l'alignement dans l'éditeur de diagramme !
Hallo nikolo,
ich habe nun mal auf win gewechselt und die ReadyToUse-Version vom 03.05. heruntergeladen:
https://download.qelectrotech.org/qet/b … dytouse.7z
Damit erziele ich das gleiche gute Ergebnis wie mit der Debian GNU/Linux-Version. Siehe Anhang!
Damit zerschlägt sich auch die Hoffnung, daß es etwas win-Spezifisches sein könnte...
via Online-Translator:
Salut nikolo,
je suis maintenant passé à win et j'ai téléchargé la version ReadyToUse du 03.05. :
https://download.qelectrotech.org/qet/b … dytouse.7z.
J'obtiens ainsi le même bon résultat qu'avec la version Debian GNU/Linux. Voir l'annexe !
Ainsi, l'espoir qu'il s'agisse de quelque chose de spécifique à win s'évanouit également...
QElectroTech → Posts by plc-user
Powered by PunBB, supported by Informer Technologies, Inc.
Generated in 0.028 seconds (45% PHP - 55% DB) with 5 queries