Search options (Page 7 of 13)

Maybe here?

https://github.com/qelectrotech/qelectr … c.cpp#L165

/**
 * @brief PartArc::sceneGeometricRect
 * @return the minimum,
 * margin-less rectangle this part can fit into in scene coordinates.
 * It is different from boundingRect() because it is not supposed
 * to imply any margin,
 * and it is different from shape because it is a regular
 * rectangle, not a complex shape.
 */
QRectF PartArc::sceneGeometricRect() const
{
    return mapToScene(QetGraphicsHandlerUtility::rectForArc(m_rect, m_start_angle/16, m_span_angle/16)).boundingRect();
}

... or at least in that file?

You are right, too, Vbxler!

The definition-line of your Start-Element has these values:

hotspot_y="14" height="40" width="90" hotspot_x="45"

and shows the graphical errors.
The corrected version of the file from QET_ElementScaler has these values:

hotspot_y="15" height="40" width="110" hotspot_x="55"

and shows perfect graphics.

When I re-open the corrected file in Element-Editor and save it again, the false values are written to file again.
It seems that the calculation of hotspots and size of the element is broken in Element-Editor at the moment...

Hallo zusammen!

Meiner Meinung nach sollten wir ein gemeinsames Konzept für alle Symbole und Elemente bezüglich Größe, Aussehen, etc. erstellen.

Hatte das bereits in anderen Threads angesprochen, dass wir ein paar Regeln für die Erstellung von Symbolen brauchen und auch Vorschläge dazu gemacht. Die waren bislang überwiegend für Eigenschaften von Front-Ansichten. Wenn wir das auch für Schaltplan-Symbole hinbekämen ... umso besser!

Ich konnte mich noch nicht dazu durchringen, die vorhandenen Symbole zu überarbeiten, weil es viel manuelle Arbeit bedeutet. Mitstreiter zu haben, motiviert natürlich! 

Hier Links zu vorhandenen Diskussionen hier im Forum:
https://qelectrotech.org/forum/viewtopi … 247#p14247
https://qelectrotech.org/forum/viewtopi … 224#p14224

via online-translator:

Hello all!

In my opinion, we should create a common concept for all symbols and elements in terms of size, appearance, etc..

I had already mentioned in other threads that we need some rules for the creation of icons and also made suggestions. So far these have been mostly for front view properties. If we could do the same for schematic symbols ... all the better!

I have not yet been able to bring myself to revise the existing symbols because it means a lot of manual work. Having fellow campaigners is motivating, of course! 

Here are links to existing discussions here in the forum:
https://qelectrotech.org/forum/viewtopi … 247#p14247
https://qelectrotech.org/forum/viewtopi … 224#p14224

Hallo Olaf,

die Anleitung ist ins Programm integriert: Rufe es einfach ohne Parameter oder mit "--help" als Parameter auf:

QET_ElementScaler --help

Wenn Du einfach nur eine einzelne Element-Datei mit einem Skalierungsfaktor bearbeiten willst, ist der Aufruf ganz einfach. Zum Beispiel:

QET_ElementScaler BeispielElement.elmt 0.75

Dabei wird eine neue Datei "BeispielElement.SCALED.elmt" mit dem skalierten Element erstellt. Wenn der Speicherort der Element-Datei in der Benutzersammlung liegt, lädst Du anschließend die Benutzersammlung neu und kannst das Bauteil benutzen.

Wenn Du eine Menge Dateien in einem Verzeichnis mit demselben Faktor bearbeiten willst, benutzt Du die Batch-Datei "scale.cmd" und passt darin die Speicherorte für das Programm, die Elemente und den Faktor an.

Hallo Olaf,

schau doch mal in diesem Thread
https://qelectrotech.org/forum/viewtopi … 286#p17286
oder direkt auf meinem github-account:
https://github.com/plc-user/QET_ElementScaler

Dort gibt es eine Linux- und eine win-Version als Binary, oder Du kannst es für "Dein" System aus den Quellen selbst kompilieren.

Bei Fragen oder Anregungen:
Fragen oder anregen! 

Salut Laurent,

there is no need to compile QET_ElementScaler for windows, because that is available in the releases.
I compile my programs for Windows on ReactOS and mention it that way to support another open source project at least by advertising it a bit!
https://reactos.org

Salut Laurent,

is it a "bug" if I already write exactly that in todays introductory post?

Maybe you (someone) can give me a hint where I can find the place in the QET source code where the values for the hotspots, width and height for the definition-line are determined? Or is it somewhere described, how to determine the correct values? Then I could perhaps implement this in the short term...

when using Options other than scaling-factor and filename, you have to add the filename with "-f filename"
For example:

./QET_ElementScaler --FlipVertical -f pylone.elmt 

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!

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! 

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.

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.