401

(96 replies, posted in Scripts)

Hello Lieven,

I guess you mix two different topics:
This thread is about a commandline-tool to convert QET-Elements to SVG.
The screenshot you sent is about export of QET-Schematics.
These are different topics. You should open a new thread in the English Forum...

But to answer your question:
M$-Office would not be my first choice when it comes to dealing with SVG-Graphics!
In my opinion it would be the last choice: only if nothing useful is available, but that's another point...  nomicons/wink

You are right:
When I export a QET-Schematic to SVG there is much free space right and below of the schematic!
It seems that the picture-size in the SVG-file isn't set correctly. Export to PNG shows the correct view!
So if you want to use the export in a word-processor then maybe PNG-export would be better...
Or you edit the SVG with Inkscape before importing to office: Here you can set the document-size to the contents
(Menu -> Document-Settings -> Button... see attachment)

EDIT:
From whatever reason the width and height of the SVG is calculated too big!
I tried some different folio-sizes and exported them to SVG: It seems to be a constant factor of 16/9 = 1.7777777

With this patch all exported SVGs had the correct width and height:

diff --git a/sources/exportdialog.cpp b/sources/exportdialog.cpp
index a50c5147e..6588ecbc3 100644
--- a/sources/exportdialog.cpp
+++ b/sources/exportdialog.cpp
@@ -411,7 +411,7 @@ void ExportDialog::generateSvg(
        
        // "joue" la QPicture sur un QSvgGenerator
        QSvgGenerator svg_engine;
-       svg_engine.setSize(QSize(width, height));
+       svg_engine.setSize(QSize((width*9/16), (height*9/16)));
        svg_engine.setOutputDevice(&io_device);
        QPainter svg_painter(&svg_engine);
        picture.play(&svg_painter);

@Laurent and/or @Joshua:
Maybe one of you can check?

In the attachment you find a package with two SVGs:
one exported from original QET-Version and the other exported from my local QET-version with 9-16-patch

Best regards
  plc-user

402

(96 replies, posted in Scripts)

Salut Laurent,

as far as I understand this code fragment, this is the workaround for the font size of the old "input"-elements. I think that this code-fragment has become obsolete with my inserted part.
In my local QET version with which I opened and saved the ~4500 elements, this part of code was also active. It didn't do any harm!
But Joshua will know exactly!

Best regards,
  plc-user

If the slave-element is defined to have "switch state" defined as "other" then there is no reference shown with the master!

404

(96 replies, posted in Scripts)

Salut Laurent!

In my opinion it's not a "must have", if we think about users who only need the official collection.
When we think about QET's long-standing users, that have elements created with earlier versions of QET with "input"-Elements inside, we should apply the patch.

Best regards
  plc-user

Hello jari!

There is something wrong with your <shift> - key!  nomicons/wink

Please use Forum-Search to find answers to your questions:
References in PDFs and import/export to/from CSV are asked very often...

Best regards
  plc-user

Hallo Fabian,

Wahrscheinlich wirst Du um eine SQL-Abfrage nicht herumkommen.

Probiere doch mal die Forumsuche mit den Stichwörtern "Export" und "BOM":
Da kommt ein Ergebnis zu 'nem französischen Beitrag, wo der Frager zum Schluß sehr zufrieden war.

Hallo Thorsten,

es geht ja hier nicht darum, irgendwelche Verweise zu machen. Das Verweis-Element bietet nur die Möglichkeit, die gewünschten Informationen anzuzeigen. Im Anhang ein Beispiel, wie das aussehen kann.

-----------

This is not about making any references. The link element only offers the option of displaying the desired information. Attached is an example of how this can look.

408

(96 replies, posted in Scripts)

This is getting more and more interesting: Another ~500 views on this topic and still no feedback that one or the other element doesn't work.
It's not that I'm looking for special thanks or fishing for compliments: I asked for "proofreaders".
You didn't want it any other way: I will "release" the pull request with the changed elements after all.

As said before: To say nothing is to agree!

Best regards
  plc-user

Hallo Thorsten,

versuche doch mal eine Forum-Suche mit dem englischen Begriff für "Leiterquerschnitt": gauge

Vor nicht allzulanger Zeit kam dieselbe Frage schon mal auf und darauf hat Laurent geantwortet.

Gruß
  plc-user


PS:
Mit deutsch bist Du im englischen Sub-Forum irgendwo falsch abgebogen...  nomicons/wink

Hallo Andi,

andi11 wrote:

thank's very much.
i thought that it's drawn wie QET elements out of the library. But you used just basic lines and stuff like that, clever solution.
Is there a way to draw it with conductors? That way i should have an place to keep metadata, like purpose of signal.

irgendjemand muss mit einem Element anfangen:
Vielleicht ist dies ja der Anfang von einem großen BUS-Unterverzeichnis?  nomicons/wink

Gruß
  plc-user

411

(96 replies, posted in Scripts)

Hello everybody!

In this post https://qelectrotech.org/forum/viewtopi … 380#p19380 I asked the forum participants to try out the elements they use most often and give feedback on whether they are OK.
After eight weeks of waiting, I am a little surprised:
There was no feedback on the elements!

That can mean two things:
No one has checked them or there is nothing wrong with them.

In German, we have a saying:
To say nothing is to agree!

So I'll just say that the elements that I automatically updated to the current version are fine! Nevertheless, I will not release the pull-request myself:
The "four-eyes principle" should still be applied in my opinion.

Best regards
  plc-user

Für den Klemmleisten-Manager hat Laurent ja schon ein paar Anleitungen verlinkt.

Vielleicht bist Du für Fragen zum Python-Plugin hier besser aufgehoben?
https://qelectrotech.org/forum/viewforum.php?id=16

Kann es sein, dass da zwei verschiedene Möglichkeiten, Klemmleisten zu bearbeiten durcheinandergewürfelt werden?

Es gibt einmal das Python-Plug-In, das separat installiert werden muss und über

Menü - Projekt - Klemmenplan-Plugin starten

gestartet wird und seit einiger Zeit einen von Joshua selbst entwickelten QET-internen Klemmleisten-Manager

Menü - Projekt - Klemmleisten-Manager (DEV)

(zumindest in der 0.10 Dev-Version)

HTH

SchindiSoft wrote:

Man könnte anstatt Ort natürlich auch eine andere dynamische vordefinierte Information / Funktion verwenden - Bauteil einfach nach Wunsch anpassen - is ja nicht verboten

Nützt nur nix, wenn die Software den XML-tag, den ich händisch einfüge, nicht kennt!

Ein Bauteil, das als "Klemme" definiert ist, hat keine Eigenschaft "Ort"!
Habe ich im Post von FH völlig überlesen, dass es sich um eine Klemme handelt, der er einen Ort zuweisen wollte!

If you would have used Forum-Search you would have found this thread:
https://qelectrotech.org/forum/viewtopi … 5541#p5541

Or other Threads pointing to QET_ElementScaler

416

(193 replies, posted in Import DXF)

The link works fine for me!
Do you have any speacial settings set in your browser?
Or maybe a browser-plugin prevents this site from loading?

417

(193 replies, posted in Import DXF)

I'm only on Linux, so I can't really help you with Win problems, but:
Neither program really needs to be "installed".

dxf2elmt is a command line software and is called like this:

dxf2elmt DXF-Drawing.dxf

A corresponding *.elmt file is then created.

DXFtoQET is a program with a graphical user interface and does not have an integrated installation program: This only needs to be copied to the "appropriate" location.

Ich gehe jede Wette ein, daß Du NICHT QET-Version 5.irgendwas hast!  nomicons/wink
Das ist die QT-Version, die drunter liegt oder mit der kompiliert wurde!
QET ist erst bei Version 0.10 in der Devel-Fraktion und 0.9 bei den stable-Releases.

Menü -> Hilfe -> ÜberQElectroTech

vgl. Bild im Anhang


Editieren kannst Du die Eigenschaft "Ort" im Diagramm-Editor, wenn Du das Bauteil markiert hast - siehe Bildschirmfoto.

Ah ... o.k. ... habe auch nicht daran gedacht, dass ich seit Jahren immer die aktuellsten Devel-Versionen benutze.

Deswegen ist es immer sinnvoll, bei Fehlern auch die Programm-Version mit anzugeben!

Das ist irgendwann in eine Version eingeflossen, daß man das eintragen kann.
Vielleicht versuchst Du es einfach mal mit einer aktuelleren Programmversion?

Der Einbauort kann ja nicht wirklich sinnvoll im Element selber definiert werden: Das weiß der Ersteller ja gar nicht!
Deswegen macht es meiner Meinung nach nur Sinn, das im Diagramm-Editor editierbar zu haben, wenn das Element benutzt wird.

Bitte nicht ein- und dasselbe Thema in mehreren Foren posten!

tiz.meneghe wrote:

The doubt remains whether by doing so I am NOT modifying a string which could then create a bug...

Here's where my question lies, "be able to enlarge a character" some font sizes without altering the element sizes (while still keeping the same dimensions as the original title block (columns/rows/pixes) and sheet (A4).

Then obviously how to update the elements already inserted in the sheet.

You should extend the search text to the tag that precedes it. For example

font="Sans Serif,5 

If you make the changes only in your project files (*.qet), all elements contained therein should be changed. The element collections are then not affected. Automatic reversion is not provided.
If you then want to keep those modified Elements, you can create a new collection for yourself and then also change the UUIDs like Laurent said.
But keep in mind: Have a backup of the project! nomicons/wink

Fonts have been a problem with computer systems, for ages!  Especially when it is supposed to look the same across operating systems and languages.

If you try to familiarise yourself with the subject, you will quickly find evidence that the terms "font" and "font family" are often confused!
As an example: "Sans Serif" is the description of a family of fonts that have no serifs. The actual font behind it depends on what the user has set for it on their system. The same applies to "MS Shell Dlg 2": It's a replacement-name for any font the user sets in the registry ... this can even be "Symbol" or "DingBats"!
And: The operating system supplier often sets different fonts depending on the country.

This of course makes it difficult for software developers and users to get a clear line so that it looks the same across operating systems and languages. This is particularly noticeable to users who are working on different systems.

When you search the forum for "font" and "size", you'll find tons of messages about this topic!

You want to place free text in the diagram and want to set a background-color for the text?
Placing Text is possible ... see screenshot.
For the background-color you need to do a workaround with a colored rectangle placed behind the text. (see screenshot)

What's wrong with these, for example?