You are not logged in. Please login or register.
QElectroTech → Posts by plc-user
Salut Laurent!
Thank you for the feedback!
GCC on Debian unstable and TDM-GCC on ReactOS did not show this warning.
Otherwise I would have corrected that line:
Don't like warnings when compiling code, too!
You may change Line 92 in main.h to
{0,0,0,0}
Then the warning should be gone.
EDIT (29.12.22 11:58 CET):
already changed at github - no new binaries needed for this code-change
at github I uploaded binaries for Linux and ReactOS. The ReactOS-binary works also on win.
If you compile it on other systems like macOS, etc. it will run there, too!
here a screenshot of an element:
Today I uploaded a new version of "QET_ElementScaler" to github: https://github.com/plc-user/QET_ElementScaler
It's not perfect yet, but it's getting better and better!
All graphic elements are now taken into account when mirroring!
The mirroring is done at the coordinate axes.
The texts are not (yet) in the right position, because the text-length, -width and -orientation must also be taken into account for the new position. For the values of the definition line (hotspots, ...) the way of calculation is not yet clear to me. But you have to open the new file with the element editor anyway to check or correct the positions of the texts. Then the definition line will be corrected. Take a look at the sample-file I created in the attachment.
In any case, this is already very useful as a starting point for the further processing of the component! 
I do not understand your question because it is not in English and secondly, from where do you want to download it?
Download QET, install it and all the elements available from this manufacturer are in the QET Collection.
If you want to participate and create elements, we will be happy to include them in the QET collection.
Just create them in the element editor, or use the DXF to QET converter beforehand.
no, I did the installation from the ''.exe'' file
It does not matter, how you installed QET. The question was how you start QET to use it.
Do you double-click on the executable file or do you start QET from the batch-file "Lancer QET.bat"?
When starting from the batch-file it reads some environmental settings and then it will start QET with the appropriate settings for language, etc.
Just tried on a fresh installed win10 and "ReadyToUse - QET":
Created Sub-Directories under "c:\tools\qet\conf\elements\"
placed some elmt-files in the sub-sub-directory and created a file "qet_directory" for each sub-dir.
Here it works as expected. See screenshot.
Maybe the language is not set correctly on your system?
Did you start QET from the batch-file "Lancer QET.bat"?
The folder-names are the loclised texts taken from the file "qet..." lying in that directory and not from the file-directory-name itself.
Please compare with the other directories in the QET-collection.
Just created a pull-request with your Symbol, Vbxler, and a RCBO from manufacturer "Hager".
When I understand it correctly ...
Have you tried double-click and then "right-click -> connect" ?
Good, then my world view is correct again! 
OK, will use a filename without points next time!
Edit: When compiling something the result is automatically set to be executable.
But do I have any control over the file permissions when I upload something to github? Or is it the user who sets the permissions him/herself after downloading the binary? As far as I know it's the second, isn't it?
Thank you for trying, Laurent!
I didn't think of comparing "my" file with the one you uploaded here on Sunday and have done so now. You can see the compare-result from DoubleCommander in the attached screenshot: Our binaries are amazingly identical! Amazing, because we definitely compiled on different machines and at different times. Compared a second time with "cmp" on my Debian-Box and it also says that the files are identical.
The message in your case I could imagine that the file looks like it has a file extension because of the added part after the underscore and therefore mac doesn't recognize it as an executable file? Maybe the file will be recognized when you rename it?
Does mac have an "executable-bit" for files? (chmod 744 ....)?
Just uploaded new binaries for Linux, ReactOS (win32) and macOS to github-repository:
https://github.com/plc-user/QET_Element … g/0.4beta2
maybe someone with a mac can test the new binary for mac and tell me, if it works?
as said before: I don't have any access to mac's ...
Thanks in advance!
Compile work on mac's, but mirror flip on this element isn't perfect yet.
The lines and polygons are flipped one-by-one!
That's why I say
useful during creation of elements
in the help of QET_ElementScaler and the README on github.
If we can limit ourselves (at least for now) to applying flipping and mirroring to individual polygons, I can definitely imagine this variant in QET as well!
In the context menu (right-click) there is also the possibility to add or remove points only for polygons.
Maybe this is a way to quickly integrate "flipping"? It seems to be needed every now and then, otherwise this thread would not exist...
just uploaded new source-code:
- positions for terminals are always rounded without decimals
- when removing all terminals, the "link_type" is set to "thumbnail"
sorry, I don't have any access to mac's ...
upload of new binaries for Linux and ReactOS will follow soon.
the "-" at the "std=c++17" - option was missing...
just fixed!
the sub-directories need to exist before compiling...
will add creation of sub-dirs in the shell-scripts later!
EDIT: DONE!
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.elmtThis results in a new element-file where ALL lines and polygons are flipped.
See post here: https://qelectrotech.org/forum/viewtopi … 808#p16808
Today I uploaded a new version of "QET_ElementScaler" to github: https://github.com/plc-user/QET_ElementScaler
This version is completely rewritten in C++, where I (like QET) use pugixml for handling the contents of the element files.
I made a few additions/changes that makes working with the software easier: The XML description line no longer needs to be removed afterwards!
As before, x and y scaling factors can be specified, input is via STDIN (-i) or a file (-f FILEINAME) and output is, as before, to a new file or to STDOUT (-o).
In addition, I have added the possibility to remove "terminals" from the element. This can be useful when terminals can be omitted from overloaded front views.
Furthermore, there is now the possibility to flip polygons and lines horizontally and/or vertically. This can be useful during the development of complex front views, as long as these functions are not yet available in the QET element editor.
Special care should be taken with the option "--OverwriteOriginal", because here the original file will be overwritten WITHOUT further request!
The scaled values of the new element are written into the new file with a maximum of 2 decimal places. In my view, this is completely sufficient for the display of schematic symbols and front views (thumbnails). In some elements present in the QET collection I have seen values with up to six decimal places, which in my opinion is excessive.
To "fix" such elements, QET_ElementScaler can of course be used! With the call:
QET_ElementScaler -f FILENAMEthe values are rounded to max. 2 decimal places and any font sizes with decimal places are rounded to whole numbers.
I wish all users of the software a lot of fun and success with it and would like to see bugs reported (e.g. here or at github). Of course, I also have an "open ear" for suggestions for improvement!
Best regards
plc-user
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
Stimmt, den Teil hatte ich vergessen, zu erwähnen: Kauf-Software und die mitgelieferten Dateien unterliegen meistens irgendwelchen unfreien Lizenzen!
via online-translator:
C'est vrai, j'avais oublié de mentionner cette partie : Les logiciels achetés et les fichiers qui les accompagnent sont généralement soumis à des licences non libres !
Hello Joshua,
that looks good: No more crash! Thank you!
cela a l'air bien : Plus de crash ! Merci !
Hallo Ke Chouffe,
Vielleicht ist einfach ein "Problem" mit der eingestellten Sprache, dass die Such-Funktion das passende Element nicht findet?
Versuche doch mal, die QET-Sprache auf "französisch" einzustellen:
Menu -> Einstellungen -> Sprache
(anschließend QET neu starten)
via Online-translator:
Peut-être est-ce simplement un "problème" avec la langue choisie qui fait que la fonction de recherche ne trouve pas l'élément correspondant ?
Essaie donc de régler la langue QET sur "français" :
Menu -> Paramètres -> Langue
(puis redémarrer QET)
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.
QElectroTech → Posts by plc-user
Powered by PunBB, supported by Informer Technologies, Inc.
Generated in 0.030 seconds (22% PHP - 78% DB) with 5 queries