Search options (Page 9 of 13)

In my opinion it wasn't very hard to implement a mirror- or flip-function for QET_ElementScaler!
You need a loop to walk through the x- and y-values of a polygon to get the min- and max-values.
In a second step you loop through the x-and y-values again and calculate the new x- and y-values.

These vertical and horizontal flip-functions are implemented in the new version of QET_ElementScaler!

I do not know the internals of how polygons are saved in QET internally, but I guess it should be possible to implement this with manageable effort for someone who knows the internals...

In QET_ElementScaler it is implemented this way:

double dMin = 9.99e99;
double dMax = -9.99e99;
// first FOR-Loop for x-values:
for (loop through x-values) {
    dMin = min(actValue, dMin);
    dMax = max(actValue, dMax);
}
// second FOR-Loop for x-values:
for (loop through x-values) {
    newValue = (dMin + dMax) - actValue)
} 

It may not be the most elegant way to flip or mirror elements but it works.
I have tried this flipping / mirroring on several elements and could not find any malfunctions! 

But you may try for yourself! 
Create a "scaled" QET-Element and copy-paste the flipped polygon to your Element.

you may call it like this:

QET_ElementScaler --FlipPolyHorizontal -f YourElementFile.elmt
or
QET_ElementScaler --FlipPolyVertical -f YourElementFile.elmt

This results in a new element-file where ALL lines and polygons are flipped.

See post here: https://qelectrotech.org/forum/viewtopi … 808#p16808

Hallo Thomas,

ich kann Dir leider nicht helfen, sondern möchte Deine Anforderung noch erweitern:
Es gibt auch viele Reihenklemmen mit drei Anschlußmöglichkeiten am Markt, die im Klemmenplan abgebildet werden wollen!

Gruß
  plc-user

Hello Joshua,

that looks good: No more crash! Thank you!

cela a l'air bien : Plus de crash ! Merci !

Hallo nicolas.lotito,

".xsy" bezeichnet nur die File-extension. Interessant wäre, wie die Grafik innerhalb der Datei gespeichert ist. Ist das Dateiformat irgendwo ausgiebig beschrieben? Wahrscheinlich nicht, wenn es sich um eine Bezahl-Software handelt...

Eine Benutzersammlung ist im Prinzip schon vorhanden: Sie wird aber wahrscheinlich noch leer sein (vgl. Bildschirmfoto).
Du kannst aus der QET-Sammlung Elemente einfach in die Benutzersammlung ziehen, dort per Rechts-Klick Ordner erstellen, etc.
Anschließend kannst Du die Elemente in der Benutzersammlung per Doppelklick editieren.

via online-translator:

Le fichier ".xsy" désigne uniquement l'extension de fichier. Il serait intéressant de savoir comment le graphique est enregistré à l'intérieur du fichier. Le format de fichier est-il décrit en détail quelque part ? Probablement pas s'il s'agit d'un logiciel payant...

Une collection d'utilisateurs est en principe déjà disponible : Mais elle est probablement encore vide (voir la capture d'écran).
Tu peux simplement faire glisser des éléments de la collection QET vers la collection utilisateur, y créer des dossiers par un clic droit, etc.
Ensuite, tu peux éditer les éléments dans la collection d'utilisateurs en double-cliquant dessus.

I'll be patient! 

Done:
https://qelectrotech.org/bugtracker/view.php?id=269

Hello Laurent,

I guess you misunderstood something:
This thread is not about copy-and-paste - that's the other thread I started.
This thread is about a reproducible crash of QET when inserting a text-element in element-editor!

Something seems to go wrong when saving and reloading an element and QET crashes, because the source-code-line 74 of sources/editor/ui/texteditor.cpp says so:

assert(m_change_connection.isEmpty());

(see above)

I can even reduce the steps to reproduce:

In the attachment you find the Element-File.
I edited the element-file with a text-editor to sort the elements by type and added some blank lines for readability - no changes in position-values!

EDITED
Just created a new version of QET_ElementScaler:
With the newly added optional parameter "-o" or "--stdout" it is now possible to write the scaled element-data to stdout instead of writing a renamed file.

The new option "-i" or "--stdin" allows QET_ElementScaler to be used with re-direction and/or pipes on the commandline:
The input-data is read from stdin and the output will be written to stdout.

Examples to write to stdout:
QET_ElementScaler -o InputElement.elmt 1.4 > NewScaledElement.elmt
QET_ElementScaler -o InputElement.elmt 1.4 | OtherSoftwareBinary

Examples to use re-direction and/or pipes:
QET_ElementScaler -i  1.4 < InputElement.elmt > NewScaledElement.elmt
cat  InputElement.elmt | QET_ElementScaler -i 1.4 | OtherSoftwareBinary

Have a look and give it a try:
https://github.com/plc-user/QET_ElementScaler

Hello jhonathan!

I like your rulers!

They are created with the same scale we agreed with the developers in the other thread: https://qelectrotech.org/forum/viewtopi … 155#p16155

If I understood Joshua correctly, he wants to add the possibility to display the measurement in mm directly when creating an object (line, rectangle, etc.) in the element editor.

I think it is a good way to draw mounting plates with the help of such rulers:
There are so many possible dimensions for mounting plates that it seems impossible to create all variants as a separate element. For DIN-rails (as comparable part) I only created a few in 10cm steps...
The same challenge exists for cable ducts: They even have to be adapted to the respective situation, so there can't be standard lengths either.

Hallo Andreas,

als Problem würde ich das auch nicht ansehen:
Für eine saubere Trennung von Schaltplan und Aufbaubild braucht ihr sowieso jeweils eigene Schaltplan-Symbole für die KNX-Module, weil die Aufbaubilder bekannterweise keine Anschlüsse haben....

Für die Verknüpfung von Schaltplansymbol und Front-Ansicht hat Joshua ja schon für eine spätere Version von QET eine Lösung in Aussicht gestellt. Und für die Aufteilung eines komplexeren Gerätes in mehrere Schaltplansymbole gibt es auch bereits Feature-Wishes in anderen Threads hier im Forum.

via Online-Translator:
I wouldn't consider that a problem either:
For a clean separation of the schematic and the front view, you need separate schematic symbols for the KNX modules anyway, because the front views do not have any terminals...

Joshua has already promised a solution for linking the schematic symbol and the front view in a later version of QET. And for the division of complex devicee into more than one schematic symbols, there are already feature wishes in other threads here in the forum.

Hello Joshua,

just so I understand you correctly:
What is called "front view" in the subject of this thred is what you call "thumbnail"?

These thumbnails are not supposed to appear as "duplicates" of schematic symbols in the BOM, that's right, Laurent. Then it may make sense that we also need a link between the schematic symbol and the thumbnail at some point, doesn't it?
There is Schematic-Software on the market that even goes further: They offer support for creating layout plans from the schematic, from which even drilling plans for mounting-plates are automatically generated that can be fed into a CNC. But that's still in the far future for QET!

Of course, I don't want to leave you alone with the work of scaling: You can count on my support to make the "deprecated" folder smaller! Didn't write "QET_ElementScaler" for nothing...