Search options (Page 14 of 31)

Wer oder was hindert Dich daran, den zweiten Kontakt frei auf einem beliebigen Folio zu plazieren und die beiden dann zu verknüpfen?

Hallo Foriever,

Deine Beobachtung stimmt!

Da ich das Verhalten auch nicht toll finde, habe ich mich im Quellcode auf die Suche nach der passenden Stelle gemacht und glaube, das Verhalten auch so geändert zu haben, sodass nur gescrollt wird, wenn der Text den sichtbaren Folio-Ausschnitt verlässt.
Werde bei GitHub einen PR erstellen.

online-translator:

Salut Foriever !

Ton observation est juste !

Comme je n'aime pas non plus ce comportement, j'ai cherché l'endroit approprié dans le code source et je pense avoir modifié le comportement de sorte que le texte ne défile que lorsqu'il quitte la partie visible du folio.
Je vais créer un PR sur GitHub.

Your file contains garbage!

At the end there are many lines behind the last closing tag "</project>" (see screenshot) and at line 12315 there are additional (fragments) of tags!

It seems that you once had some problems with your system? Did you switch off your system without closing all programs? Just guessing...

The log file was not as informative as hoped:
Apart from two warnings, I don't see anything unusual.

Please attach the qet-file to a post here in the forum. Unless there are any legal concerns regarding patents or company secrets!

Streiche doch mal das "-id" aus dem Schriftfeld und schreibe nur "%(folio)" da rein!

Did you notice the menu-entry just below "Import scaled element"? (see attachment!)
AND: Use the conversion-tool dxf2elmt! The other tool is VERY outdated!
You find the download-link for win64 in this post: https://qelectrotech.org/forum/viewtopi … 520#p20520

What do you want to do?
QET works with own file-formats for elements and schematics!

I think, many of your questions about scale and dxf-import will be answered, if you read in the other thread and follow the links there:
https://qelectrotech.org/forum/viewtopi … 684#p20684

As the name QET_ElementScaler might suggest, only QET-Elements can be scaled by that software!
You need to convert your dxf to a QET-Element before using QET_ElementScaler!

Hello vadoola!
Salut Laurent !

As I already wrote several times in this forum:
QET is primarily a software to draw schematic diagrams.
QET is no substitute for CAD software like LibreCAD, AutoCAD or so.
The only dimension QET "knows" is px!
These number of px can be set by every user individually for height/width of a folio.
A folio itself has no direct connection to a papersize – it can be printed to any papersize, users have a printer for.

So in my opinion we should NOT use a specific size of paper for the scaling of elements!

As I suggested several times we should use a front-view-scaling where the user can see the real size at first sight or where he/she can calculate the real size by using a simple integer factor:
1 mm <-> 2 px

1 px is also the smallest step size, a QET-Element can be moved in diagram-editor. So then we could "move" the elements by 1 px = 1/2 millimeter in real-life.

We already have a wild mixture of scaling-factors with front-views: Please don't add another!

About the texts / fonts

That wasn't meant as a negative criticism: just a remark that this is the case.
It is clear to me in particular that there is still a lot of work to be done to integrate the texts correctly into the element. You will have "a lot of fun” with the text position, because it is not directly on the baseline of the first letter, but on a bounding box that is specified by qt, but not well described...

A difference to many other software: QET can only handle font-sizes which are integer numbers!

On M$ where I don't have admin-rights I only use the "Ready-To-Use" - Version!
I use DoubleCommander to unpack and copy it to a folder in "D" and it works perfectly for some years now!
When upgrading to a new version you first have to delete the elements-folder for the case that some elements are moved from one folder to another AND you have to prevent the config-folder from overwriting.

Hello Vadoola!
Salut Laurent !

That's a great step forward, Vadoola!

It looks very good, but unfortunately I have to say that the dimensions are not yet right. There's a factor of 10/3 in there somewhere with the part I used. The attached part has the dimensions 60 x 210 mm, but the resulting element is 200 x 700 px.

And when I look at the texts that come out of a previously used example (05DI-AD16DIX-10.dxf): There the font is not correct yet and the font height is not set either, so QET uses the default size 9 when opened.
This is how it looks now (formatted by hand!)

        <dynamic_text x="35.12" y="-11.14" z="0" rotation="0" 
            uuid="{51347e64-514a-47dc-8c7f-aa180de58afd}" 
            font="Arial Narrow" 
            Halignment="AlignHCenter" Valignment="AlignVCenter" 
            text_from="UserText" frame="false" text_width="-1" color="#000000">
            <text>\C7;\fArial|b0|i0|;\H0.030335398390889;All Connectors 
are Located 
Under Gullwing 
Covers</text>
        </dynamic_text>

When I look at the texts in the converted element, I think that this would be correct for the text, font and font height:

        <dynamic_text x="35.12" y="-11.14" z="0" rotation="0" 
            uuid="{51347e64-514a-47dc-8c7f-aa180de58afd}" 
            font="Arial,3" 
            Halignment="AlignHCenter" Valignment="AlignVCenter" 
            text_from="UserText" frame="false" text_width="-1" color="#000000">
            <text>All Connectors 
are Located 
Under Gullwing 
Covers</text>
        </dynamic_text>

The font-size of "3" in this example has of course to be set to the correct value: I chose a reasonable value here.

If I understand your problem correct, you have to choose "New template (enter its name)" and then you can edit the filename.
see screenshots

I use latest QET dev-version with Debian/GNU Linux (unstable).