Search options (Page 20 of 29)

2023-12-31 19:03:39

Sicher gibt es eine Forumssuche!

2023-12-31 13:34:52

So macht OpenSource Spaß: Jeder gibt einen Teil seines Wissens / seiner Erfahrung dazu!

-----

This is how OpenSource is fun: Everyone contributes a part of their knowledge / experience!

2023-12-31 13:31:37

Hast Du welche beigesteuert, die veröffentlicht werden dürfen? nomicons/wink

2023-12-31 13:29:19

Das geht nur im Element-Editor - im Diagramm-Editor geht das nicht.

-----

Cela n'est possible que dans l'éditeur d'éléments - ce n'est pas possible dans l'éditeur de diagrammes.

2023-12-26 23:09:53

Given a directory structure with QET elements and the SVG images derived from them.
Here is a script that goes through this directory structure and links all subdirectories and SVG files.
The links of the SVG files point to the corresponding QET element.

#!/bin/bash

# to be able to process blanks in file names - remember original state:
OFS=$IFS
# set new:
IFS="
"

BaseDir="elemente"

for d in `find $BaseDir -type d | sort`; do
  echo "processing directory $d"
  # html-Header:
  echo "<html><body>" > $d/index.html
  # Unterverzeichnisse auflisten:
  for sd in `find $d -maxdepth 1 -type d | sort`; do
    if [[ "$d" == "$sd" ]] ; then
      continue
    fi
    echo "sub-dir: $sd"
    echo "<a href=\"`basename $sd`/index.html\">`basename $sd`</a><br>" >> $d/index.html
  done
  # SVG-Dateien auflisten:
  for f in  `find $d -maxdepth 1 -name "*.svg" | sort` ; do
    echo "file: `basename $f`"
    svgdatei=`basename $f`
    elmtdatei="${svgdatei%.svg}.elmt"
    echo "<a href=\"$elmtdatei\">${svgdatei%.svg}<br> <img src=\"$svgdatei\" /></a><br>" >> $d/index.html
  done
  # html-Footer:
  echo "</body></html>" >> $d/index.html
  echo ""
done

# blanks in filenames - back to original:
IFS=$OFS
# DONE!

@Laurent:
In the context of writing the script, I noticed, that a scaling-factor of 5.0 will be in many cases too much!
But I will implement your idea of including the scaling-factor to the script on github!

2023-12-23 20:07:52

Just for the record:

diff --git a/sources/editor/graphicspart/partdynamictextfield.cpp b/sources/editor/graphicspart/partdynamictextfield.cpp
index bb261287c..311102742 100644
--- a/sources/editor/graphicspart/partdynamictextfield.cpp
+++ b/sources/editor/graphicspart/partdynamictextfield.cpp
@@ -176,6 +176,12 @@ void PartDynamicTextField::fromXml(const QDomElement &dom_elmt) {
                font_.fromString(dom_elmt.attribute("font"));
                setFont(font_);
        }
+       else if (dom_elmt.hasAttribute("font_size")) {
+#if TODO_LIST
+#pragma message("@TODO plc-user: remove again, when elements are converted!")
+#endif
+               setFont(QETApp::dynamicTextsItemFont(dom_elmt.attribute("font_size", QString::number(9)).toInt()));
+       }
        else {
 #if TODO_LIST
 #pragma message("@TODO remove in futur")

2023-12-22 15:29:25

May I suggest to sort the list alphabetically?
So one can find (missing?) languages "at first sight":

lupdate -noobsolete qelectrotech.pro -ts lang/qet_{ar,be,ca,cs,da,de,el,en,es,fr,hr,hu,it,ja,mn,nb,nl,pl,pt,pt_br,ro,ru,sk,sl,sr,tr,uk,zh}.ts

2023-12-22 11:28:20

paulitajohnson wrote:

Why do I use this key combination but it doesn't work?

Manchmal liegt es daran, welches Betriebssystem mit welchen Spracheinstellungen Du hast, ob Tastenkombinationen funktionieren, oder eben nicht.
Bei Dir scheint es der Fall zu sein.
Aber dafür gibt es ja immer noch den Knopf in der Werkzeugleiste.

-----------

Sometimes it depends on which operating system with which language settings you have whether key combinations work or not.
This seems to be the case for you.
But there is always the button in the toolbar.

2023-12-22 02:05:48

Habe im Quellcode des Element-Editors eine Stelle gefunden, an der ich eingreifen kann, um auch die dynamischen Texte korrekt einlesen zu können, deren Schriftgröße mit dem Tag "font_size" gekennzeichnet sind (siehe BugTracker).
Mit der Version des Element-Editors habe ich nun alle Elemente, die mit einer Programmversion kleiner 0.8 erstellt wurden, in der aktuellen Version abgespeichert. Dabei habe ich die XRef-Elemente, bei denen Laurent mitgeholfen hat, nicht mehr angefasst!
Die etwa 4600 geänderten Elemente liegen nun vorerst nur in meinem Fork des Elemente-Repositories bei GitHub:
https://github.com/plc-user/qelectrotech-elements
Ich möchte nun alle Leser und Benutzer aufrufen, diese Elemente auszuprobieren und zu testen, ob "ihre" Elemente so aussehen und funktionieren, wie erwartet! Die Absicht war, nichts am Element zu ändern, aber man kann ja nie wissen.
Bitte gebt Rückmeldung in diesem Forum, damit wir "Altlasten" auch mal loswerden können. Zumindest bei den Dateiversionen der Elemente...

Danke im Voraus!

Und: Danke, Laurent, für Deine großartige Unterstützung!

now the same in English via Online-Translator:

I have found a place in the source code of the element editor where I can intervene in order to be able to correctly read in the dynamic texts for which the font size is marked with the "font_size" tag (see BugTracker).
With the version of the element editor, I have now saved all elements that were created with a program version smaller than 0.8 in the current version. I have not touched the XRef elements that Laurent helped with!
The approximately 4600 changed elements are currently only in my fork of the element repository at GitHub:
https://github.com/plc-user/qelectrotech-elements
I would now like to call on all readers and users to try out these elements and test whether "their" elements look and work as expected! The intention was not to change anything in the element, but you never know.
Please give feedback in this forum so that we can get rid of "old burdens". At least with the file versions of the elements...

Thanks in advance!

And: Thank you, Laurent, for your great support!

2023-12-21 17:46:47

There are only "a few" elements with this combination of tags: nomicons/cwy

$ grep -R "dynamic_text" . | grep "font_size" | awk  '{ print $1 }' | sort | uniq | wc -l
67
$

2023-12-21 16:53:56

As written in BugReport, the bug must be there since several releases:
The ReadyToUse-Version from November 15th and even the 0.9 AppImage from January this year show the same effects. I can't go further in history. I guess it was when the tags of "dynamic_text" were re-worked...

EDIT:
It's not when editing the texts: Opening the file is all you have to do to see the bug.

2023-12-21 16:41:43

Thanks, Laurent for the hints!

Just reverted the PRs #8 and #9 nomicons/sad

What do you think: Do we have the chance for a BugFix of this mal-function in Element-Editor?

2023-12-21 15:55:10

Salut Laurent !

Unfortunately, I had to create a bug report for the element editor:
The font sizes of the "dynamic_text" of older file formats are not handled correctly since some programme versions (see BugTracker). I have tested with the current DEV version and the 0.9 AppImage for Linux.

When the bug has been fixed, I will of course reapply my scripts to the original elements! But how do we proceed until then? I don't yet have enough experience with GitHub to be able to revert the current changes myself.

Sorry for the bad news!

2023-12-20 21:24:23

Having fewer different individual parts inside the QET-Elements helps with multiline-Text for SVG-converting, too!
Especially for text-parts! See attachment! nomicons/smile

[Edit]:
Just uploaded sources and created a new beta-release of QET_ElementScaler for Debian Bookworm, win32 and win64 at GitHub:
https://github.com/plc-user/QET_ElementScaler

2023-12-20 13:10:58

Ok!

Then: Let's publish the changes!

2023-12-20 08:55:31

Salut Laurent,

ok ... understood and changed that for elements that only have one "dynamic_text" like the samples above.

What about the elements that have a contact with numbers like this one with some more "dynamic_text"?

<definition hotspot_y="26" width="30" version="0.100.0" type="element" height="50" link_type="next_report" hotspot_x="17">
<uuid uuid="{8e4fac98-05b1-4f6a-be61-8559b7b5789a}"/>
<names>
<name lang="it">Contatto NC</name>
<name lang="cs">Rozpínací kontakt NC</name>
<name lang="fr">Contact NC</name>
<name lang="nl">ref volgend complex contact (NC)</name>
<name lang="es">Contacto NC</name>
<name lang="pl">Zestyk rozwierny</name>
<name lang="en">complex contact NC</name>
</names>
<informations>autor: paul deelen
licencja: zobacz http://qelectrotech.org/wiki/doc/elements_license</informations>
<description>
<dynamic_text font="Sans Serif,4,-1,5,25,0,0,0,0,0" text_width="-1" keep_visual_rotation="false" frame="false" Halignment="AlignLeft" x="-23" rotation="0" text_from="UserText" z="1" uuid="{5ede35ec-f568-47de-9ee3-5cb8ae7ff744}" Valignment="AlignTop" y="8">
<text>12</text>
</dynamic_text>
<dynamic_text font="Sans Serif,5,-1,5,50,0,0,0,0,0" text_width="-1" keep_visual_rotation="false" frame="false" Halignment="AlignLeft" x="-23" rotation="0" text_from="UserText" z="2" uuid="{06a8d219-aa9f-4133-b285-c276975af1f5}" Valignment="AlignTop" y="-25.5">
<text>11</text>
</dynamic_text>
<polygon y3="-10" x2="-10" x1="-10" y2="10" style="line-style:normal;line-weight:normal;filling:none;color:black" antialias="true" y1="20" closed="false" x3="-4"/>
<line x2="-3" x1="-10" y2="-9" style="line-style:normal;line-weight:normal;filling:none;color:black" length2="1.5" antialias="false" y1="-9" length1="1.5" end2="none" end1="none"/>
<line x2="-10" x1="-10" y2="-9" style="line-style:normal;line-weight:normal;filling:none;color:black" length2="1.5" antialias="false" y1="-20" length1="1.5" end2="none" end1="none"/>
<dynamic_text font="Sans Serif,10,-1,5,50,0,0,0,0,0" text_width="-1" keep_visual_rotation="false" frame="false" Halignment="AlignLeft" x="-2" rotation="0" text_from="ElementInfo" z="6" uuid="{30a611c8-4454-4c09-95dd-8706dab6053e}" Valignment="AlignTop" y="-12.5">
<text>/</text>
<info_name>label</info_name>
</dynamic_text>
<terminal x="-10" type="Generic" uuid="{5746597c-3494-4922-9747-b8d1512da17c}" orientation="n" name="" y="-20"/>
<terminal x="-10" name="" type="Generic" uuid="{3a8a0eed-90d6-4948-a59f-96dafaa4dc31}" orientation="s" y="20"/>
</description>
</definition>

Do we need to change this from text_from="UserText" to text_from="ElementInfo", too ?

2023-12-19 20:57:24

scorpio810 wrote:

source of text: element information
/
Label

Done!

2023-12-19 20:32:10

Ok ... the hacks with text-editor seem to work! nomicons/smile
All Elements which contained "input" are updated with current QET-Element-Editor (and Text-Editor)!

PullRequest is on the way!

2023-12-19 18:29:43

scorpio810 wrote:

these elements serve as folio reports and allow you to link two different components, (...).

Don't get me wrong: I want to keep these elements!
All I want is to get rid of those "input" inside the elements and replace them with "dynamic_text" to have elements that were created using the current version of element-editor!

In the attachment you find a *.tar.gz with updated elements.
Would someone who uses them regularly please test if they work as expected?

If so, I'll create a PullRequest with all 4089 updated Elements.

2023-12-19 12:12:21

Salut Laurent !

I searched the elements-directory and found 4089 Elements with "input", which was the old element-part of actual "dynamic_text".

As explained above: Then I opened all of them in Element-Editor and saved them again in the actual file-format.
Some of the files represent References, which caused errors when trying to save: see screenshot in attachment.
I also attached these files in a *.tar.gz.

I might create a PullRequest at GitHub to update the QET-Elements which could be saved without errors.
Do you think I should, Laurent? Would be a bigger change ... nomicons/wink

Best regards
plc-user

2023-12-18 13:54:17

Texts are there but with font-size=0 nomicons/sad

The tags for font-size in "input" and "dynamic_text" are different: Fixed that in source-code of QET_ElementScaler.

[Edit]:
Just as a question:
Do we have the option of using the element editor with command line parameters?
"Open" in the old file format and "Save to a file" in the current file format would be sufficient.

2023-12-18 09:50:29

A "big hammer" isn't always the best tool: nomicons/wink
I re-worked the sources of entity-converter to be a bit "milder".
Now letters with accents and unicode should (!) work again.

2023-12-16 19:48:28

First version with translating html-entities is available as Source on github.
It's the first "brute-force"-version that's far from perfect. nomicons/wink
If someone knows if I can use the pugi-internal function "text_output_escaped" for this, please let me know!

In this context I corrected an error with text-size of "dynamic_text".

2023-12-16 19:08:44

Salut Laurent !

Thank you for testing that function!

You found an element that contains text with characters that have to be converted to a HTML-Entity. In this case: "&"
That's one thing that is not covered, yet.

I'm working on it!

2023-12-16 13:17:29

In another context I recommended the "Eaton Schaltungsbuch" formerly known as "Klöckner-Möller-Schaltungsbuch" nomicons/wink

https://qelectrotech.org/forum/viewtopi … 215#p19215

There you find on PDF-page 504 that it should be EN IEC 81346-2 (see attachment)
On page 10-3 there are some examples from that standard.
But I don't know if QET follows this standard 1:1 ...

Search options (Page 20 of 29)

Posts found: 476 to 500 of 718

476 Reply by plc-user 2023-12-31 19:03:39

Re: Réduire la taille des éléments (4 replies, posted in FR : Aide, suggestions, discussions, ...)

477 Reply by plc-user 2023-12-31 13:34:52

Re: QET-Element to SVG (96 replies, posted in Scripts)

478 Reply by plc-user 2023-12-31 13:31:37

Re: Loxone Miniserver Symbole (4 replies, posted in DE : Hilfe, Vorschläge, Unterhaltungen...)

479 Reply by plc-user 2023-12-31 13:29:19

Re: Réduire la taille des éléments (4 replies, posted in FR : Aide, suggestions, discussions, ...)

480 Reply by plc-user 2023-12-26 23:09:53

Re: QET-Element to SVG (96 replies, posted in Scripts)

481 Reply by plc-user 2023-12-23 20:07:52

Re: QET-Element to SVG (96 replies, posted in Scripts)

482 Reply by plc-user 2023-12-22 15:29:25

Re: Second User-Collection (13 replies, posted in Code)

483 Reply by plc-user 2023-12-22 11:28:20

Re: [Suggestion] Delete superfluous waypoints (4 replies, posted in DE : Hilfe, Vorschläge, Unterhaltungen...)

484 Reply by plc-user 2023-12-22 02:05:48

Re: QET-Element to SVG (96 replies, posted in Scripts)

485 Reply by plc-user 2023-12-21 17:46:47

Re: QET-Element to SVG (96 replies, posted in Scripts)

486 Reply by plc-user 2023-12-21 16:53:56

Re: QET-Element to SVG (96 replies, posted in Scripts)

487 Reply by plc-user 2023-12-21 16:41:43

Re: QET-Element to SVG (96 replies, posted in Scripts)

488 Reply by plc-user 2023-12-21 15:55:10

Re: QET-Element to SVG (96 replies, posted in Scripts)

489 Reply by plc-user 2023-12-20 21:24:23

Re: QET-Element to SVG (96 replies, posted in Scripts)

490 Reply by plc-user 2023-12-20 13:10:58

Re: QET-Element to SVG (96 replies, posted in Scripts)

491 Reply by plc-user 2023-12-20 08:55:31

Re: QET-Element to SVG (96 replies, posted in Scripts)

492 Reply by plc-user 2023-12-19 20:57:24

Re: QET-Element to SVG (96 replies, posted in Scripts)

493 Reply by plc-user 2023-12-19 20:32:10

Re: QET-Element to SVG (96 replies, posted in Scripts)

494 Reply by plc-user 2023-12-19 18:29:43

Re: QET-Element to SVG (96 replies, posted in Scripts)

495 Reply by plc-user 2023-12-19 12:12:21

Re: QET-Element to SVG (96 replies, posted in Scripts)

496 Reply by plc-user 2023-12-18 13:54:17

Re: QET-Element to SVG (96 replies, posted in Scripts)

497 Reply by plc-user 2023-12-18 09:50:29

Re: QET-Element to SVG (96 replies, posted in Scripts)

498 Reply by plc-user 2023-12-16 19:48:28

Re: QET-Element to SVG (96 replies, posted in Scripts)

499 Reply by plc-user 2023-12-16 19:08:44

Re: QET-Element to SVG (96 replies, posted in Scripts)

500 Reply by plc-user 2023-12-16 13:17:29

Re: Cable and connector reference designators according to standard EN IEC (3 replies, posted in EN : Help, suggestions, discussions, ...)

Posts found: 476 to 500 of 718