Search options (Page 12 of 31)

Ja, im Moment ist das leider so!

Und ich glaube, das steht auch nicht ganz oben auf der Prioritätenliste, wenn der Haupt-Entwickler wieder voll einsatzfähig ist.
Es besteht natürlich immer die Möglichkeit, jemanden zu finden, der C++ unter Qt programmieren kann und Spaß daran hat, an QElectroTech mitzuarbeiten! Vielleicht kennst Du jemanden, stefan.123? Oder vielleicht kannst Du selber teilnehmen?

Ich finde es immer sehr schade, wenn hier nach neuen supertollen Funktionen gefragt wird, aber scheinbar niemand bereit ist, sein/ihr Wissen und Können hier im Projekt einzubringen.

Ich bin hier auch ganz langsam angefangen und habe Fragen gestellt und inzwischen traue ich mich daran, bestehende Funktionen zu hinterfragen und bearbeiten! Und einige davon sind bereits in QET eingeflossen...

Das geht nicht gegen Dich, stefan.123!!!
Ich wollte das nur mal loswerden...

Gruß
  plc-user

I'm a little envious: I don't have 48 cores! 

Hello vadoola,

It's good that we agreed on the scaling after all! I knew there was a misunderstanding somewhere... but didn't see
Sometimes I have to read the documentation and comments in the source code several times, too: the language barrier (French, English, German, ...) is sometimes quite high and with sharp edges!

Take your time for the realization!
As we say in German: "Gut Ding braucht Weile!"
‘Good things take time!’

If you look at the “imperial” DXF from last week:
Which one matches the original sizes better?

I know that we won't be perfect with text-size, because for elements we have to round to integer numbers, but I think we should be as close to the original as possible!

Salut Laurent !

Thanks again, Laurent!
The Debian-Version is also working pretty good!

A few questions about "qet_tb_plugin":
As I understand correctly, the plugin may or even can only be started, when a project is loaded, correct?
"qet_tb_plugin" or "qet_tb_plugin.exe" is an executable file, right?
And:
Similar to dxf2elmt or QET_ElementScaler QET only starts the executable from known locations ... QET does not download python or source-code of the plugin, right?

If all three answers are "yes", some of the "spaghetti-code" in qetdiagrameditor.cpp can be simplified and "automated" similar to configDir() or dataDir().
Already making first attempts...

Hello vadoola,

Just to understand you correctly:
You think the calculation of the text size is correct if a text that fits well into a rectangle in the DXF is much bigger and no longer fits into the same rectangle in the converted element? And that's because it says somewhere that a px is not as big as a pt? Seriously?

Attached is another example to clarify what I mean:
A DXF file in which I have inserted an 11 mm high text into a field of about 12 mm. Next to it is the converted element file, where you can see that the text “11 mm” definitely does not fit into the same field. In addition, the element file in which I changed the text “11 mm” to the appropriate size “22” and moved it.
I am explicitly not talking about the text position here, as we both know that this does not yet fit: I'm talking about the text size!

Note:
I used dxf2elmt - sources from last weeks commit c3a5b2a.

Back to the topic: 

Hello Vadoola,

I'm not quite happy with the font sizes yet.
That's why I used Inkscape to create a drawing with different font sizes. When I realized that the fonts were exported as polygons into DXF, I used LibreCAD to add some MText in different sizes.
I then converted the DXF into an element and realized that the font sizes did not fit.
If we focus on the 20 mm font:
In LibreCAD (black background) it is good to see that both texts are the same size - I expect the same for the element.
In the element (white background), the polygon 20 mm are 40px high, but the 20 mm text has a font size of 57.
So there is still a factor of about 1.4 somewhere in there that doesn't belong.
I noticed something similar with the imperial DXF from your American compatriot.

Packed all files into attached zip.

Remark #1:
The Text-Positions ... 

Remark #2:
When saving the DXF from Inkscape, the bottom edge of the rectangle was lost somewhere. That shouldn't bother you!

Salut Laurent !

What I noticed when using the ReadyToUse version for Windows:
We haven't quite finished setting the directories for configuration and data yet.
One small detail is still missing:
A command line parameter for specifying a data directory!

If we want to keep the “ReadyToUse” version for Windows as a “portable” version as far as possible, in which all files are located under ONE base directory, we need the command line parameter “--data-dir” in the batch file. Otherwise, the log files and data are not stored in the directory of the ReadyToUse version, but in the standard Windows data directory.

As an additional benefit, we offer users the option of running completely separate versions on one PC! It would only need to be called with different parameters for “--config-dir” and “--data-dir” and completely different configurations and data are possible.
And this applies in particular to all macOS and Linux users:
Here the configuration is available as “QElectroTech.conf”, which is also located in the configuration directory. Win users have the disadvantage with the registry...

Will upload the changes to my fork of QET very soon ... stay tuned! 

I have also noticed that we (still) supply a “QElectroTech.conf” with the ReadyToUse version, which is known not to be used on Windows. This can therefore be removed?

For the record and users who run Debian GNU/Linux unstable:

apt-key is not available in Debian unstable anymore!

For a few days now, this is the way to go:

• download key-file:
  wget -q https://debian.qelectrotech.org/qet/bui … sitory.asc
  and save (as root) to /etc/apt/keyrings

• adjust sources-list entry for QElectroTech
  file needs the ending ".sources" as in this example:
  /etc/apt/sources.list.d/qelectrotech.sources

• content of qelectrotech.sources:

# draw electric diagrams with QElectroTech
# 
Types:      deb
URIs:       https://debian.qelectrotech.org/qet/builds/debian/
Suites:     unstable
Components: main
Enabled:    yes
Signed-By:  /etc/apt/keyrings/Qelectrotech_Repository.asc

• from here everything further is known:
  apt update
  apt install qelectrotech

@scorpio810:
Maybe you can update the information on QET-Homepage, Laurent?
Thanks in advance! 

A short manual for the transition from old to new locations of config- and data-directories.

In the following blocks you find the changes, that have to be made by the user, when upgrading to the new version.
If you are missing any information or have found an error, please let us know!

Modifications on Linux:
- location of QElectroTech.conf:
  ~/.config/QElectroTech/QElectroTech.conf
  NO activity required!
- location of QET-stalefiles
  ~/.local/share/stalefiles/QElectroTech
  NO activity required!
- python-plugin "qet_tb_generator"
  binary of plugin may be moved to ~/.local/share/QElectroTech/QElectroTech/binary
  but generally: NO activity required!

Linux old                         -->  Linux new
~/.qet/*.json                     -->  ~/.config/QElectroTech/QElectroTech/*.json
~/.qet/element_texts_pattern/*.*  -->  ~/.config/QElectroTech/QElectroTech/element_texts_pattern/*.*
~/.qet/*.log                      -->  ~/.local/share/QElectroTech/QElectroTech/*.log
~/.qet/elements_cache.sqlite      -->  ~/.local/share/QElectroTech/QElectroTech/elements_cache.sqlite
the following directories: including content!
~/.qet/binary                     -->  ~/.local/share/QElectroTech/QElectroTech/binary
~/.qet/elements                   -->  ~/.local/share/QElectroTech/QElectroTech/elements
~/.qet/elements-company           -->  ~/.local/share/QElectroTech/QElectroTech/elements-company
~/.qet/titleblocks                -->  ~/.local/share/QElectroTech/QElectroTech/titleblocks
~/.qet/titleblocks-company        -->  ~/.local/share/QElectroTech/QElectroTech/titleblocks-company

--------------------------------------------------------------------------------

Modifications on Windows (ReadyToUse):
- Configuration and data:
  NO activity required
- python-plugin "qet_tb_generator"
  binary of plugin may be moved to  (base-dir)\conf\binary
  but generally: NO activity required!

--------------------------------------------------------------------------------

Modifications on Windows (Installer):
- QElectroTech.conf:
  NO activity required: Registry
- QET-stalefiles
  NO activity required!
- python-plugin "qet_tb_generator"
  binary of plugin may be moved to  (+)\Roaming\QElectroTech\QElectroTech\binary
  but generally: NO activity required!

To keep line-length short:
  "(#)" means "C:\Users\<USER>\Application Data"
  "(+)" means "C:\Users\<USER>\AppData"

Windows old                        -->  Windows new
(#)\qet\*.json                     -->  (+)\Local\QElectroTech\QElectroTech\*.json
(#)\qet\element_texts_pattern\*.*  -->  (+)\Local\QElectroTech\QElectroTech\element_texts_pattern\*.*
(#)\qet\*.log                      -->  (+)\Roaming\QElectroTech\QElectroTech\*.log
(#)\qet\elements_cache.sqlite      -->  (+)\Roaming\QElectroTech\QElectroTech\elements_cache.sqlite
the following directories: including content!
(#)\qet\binary                     -->  (+)\Roaming\QElectroTech\QElectroTech\binary
(#)\qet\elements                   -->  (+)\Roaming\QElectroTech\QElectroTech\elements
(#)\qet\elements-company           -->  (+)\Roaming\QElectroTech\QElectroTech\elements-company
(#)\qet\titleblocks                -->  (+)\Roaming\QElectroTech\QElectroTech\titleblocks
(#)\qet\titleblocks-company        -->  (+)\Roaming\QElectroTech\QElectroTech\titleblocks-company