Hi,
my repo is only for devel version.
You could try this :

flatpak install --user https://dl.flathub.org/build-repo/45176/org.qelectrotech.QElectroTech.flatpakref

https://github.com/flathub/flathub/pull … -831565755

2,302

(224 replies, posted in News)

Some of our users are having trouble uploading our binaries to our site, so another repo has been hosted on Github.

https://github.com/qelectrotech/qelectr … -2021%2F05

For 0.8 version see here :
https://github.com/qelectrotech/qelectr … /tag/0.8.0

Enjoy . nomicons/wink

2,303

(49 replies, posted in Videos howto)

On Linux just run qelectrotech in terminal, open your project, after launch qet_tb_generator plugin by QET menu.

ok, is project problem, run qet_tb_generator in an terminal for possible saw where are error?

You can share your project?

2,307

(0 replies, posted in Scripts)

https://github.com/kedema/qet

On OSX you need to upgrade to python 3.9 for last 0.9-dev

I tried quickly on a fresh Big Sur 11.3 VM.
https://download.qelectrotech.org/qet/forum_img_2/big_sur2.png
https://download.qelectrotech.org/qet/forum_img_2/big_sur3.png

Get https://www.python.org/ftp/python/3.9.4 … sx10.9.pkg
1 Install python 3.9
2 run Profile.command script

Install qet_tb_generator

pip3 install qet_tb_generator

Open industrial.qet example and launch plugin to see if it's work

Bonjour,

https://download.qelectrotech.org/qet/m … _name.html

Hi Unalcade,
thanks, but
https://www.virustotal.com/gui/file/014 … /detection

BTW, Joshua is working on it right now on new teminal block.

I don't saw elements like it, but uou could draw yourself.

2,313

(224 replies, posted in News)

Bientôt vous pourrez lancer des application Linux en GUI dans vos Windows..
https://www.nextinpact.com/article/4684 … que-et-gpu
https://www.01net.com/actualites/window … 41652.html

Je pense que le dernier commit fixe le problème de décalage des bornes dans une config Multi-écran avec différentes échelles.
Tu pourras essayer?

https://www.windowscentral.com/how-view … windows-10

https://git.tuxfamily.org/qet/qet.git/c … 73d0fcd2f4
https://download.qelectrotech.org/qet/b … 1-04-21-1/

Tu peux essayer de rajouter dans le script de démarrage
-platform windows:dpiawareness=0

https://bugs.launchpad.net/mudlet/+bug/1652413

https://qelectrotech.org/wiki_new/doc/o … config-dir

2,319

(224 replies, posted in News)

- Log -----------------------------------------------------------------
commit b6cfc8c755a70f2e1b98fe0b991c7599d25a5679
Author: joshua <Joshua@>
Date:   Sun Apr 18 20:03:13 2021 +0200

    Improve element collection loading time
   
    According to Qt creator flame graph, call QSettings take lot of time.
    When loading the element collection, each items of the collection get
    the current language by calling the function QString
    QETApp::langFromSetting().
    This function instantiate a QSettings object each time and take a lot of
    time.
    Now the QSettings is instantiate only at the first call, and the value
    is stored in memory, then all other call of the function don't
    instantiate a QSettings, but just return the value in memory.


you see time improvement of loading on Windows?

Chose étrange, l'éditeur d'éléments ne présente pas ce problème! De même, lors de l'exportation en PDF, pas de problème.

https://qelectrotech.org/bugtracker/view.php?id=150
https://git.tuxfamily.org/qet/qet.git/t … w.cpp#n188

Si tu peux tester en rajoutant dans le main.cpp
qputenv("QT_ENABLE_HIGHDPI_SCALING", "1");
QGuiApplication::setHighDpiScaleFactorRoundingPolicy(Qt::HighDpiScaleFactorRoundingPolicy::PassThrough);

https://doc.qt.io/qt-5/qt.html#HighDpiS … olicy-enum


--- sources/main.cpp
+++ sources/main.cpp
@@ -175,6 +175,13 @@ int main(int argc, char **argv)
#pragma message("@TODO remove code for QT 6 or later")
#endif
#endif
+
+#if QT_VERSION >= QT_VERSION_CHECK(5, 14, 0)
+qputenv("QT_ENABLE_HIGHDPI_SCALING", "1");
+QGuiApplication::setHighDpiScaleFactorRoundingPolicy(Qt::HighDpiScaleFactorRoundingPolicy::PassThrough);
+#endif
+
+
     SingleApplication app(argc, argv, true);
#ifdef Q_OS_MACOS
     //Handle the opening of QET when user double click on a .qet .elmt .tbt file





Compiler QET sur Windows
https://qelectrotech.org/forum/viewtopi … 999#p12999
https://qelectrotech.org/wiki_new/doc/qt_pour_windows

ou
https://qelectrotech.org/wiki_new/winstatic/winstatic

https://doc.qt.io/qt-5/highdpi.html
https://lists.qt-project.org/pipermail/ … 37434.html
https://programmersought.com/article/27635311665/

The QT_ENABLE_HIGHDPI_SCALING environment variable, introduced in Qt 5.14, enables automatic scaling based on the pixel density of the monitor. Replaces QT_AUTO_SCREEN_SCALE_FACTOR.

The QT_SCALE_FACTOR_ROUNDING_POLICY environment variable and QGuiApplication::highDpiScaleFactorRoundingPolicy API, introduced in Qt 5.14, makes it possible to control if and how the device pixel ratio should be rounded to the nearest integer. This is relevant for configurations like Windows at 150% scale. Possible values are Round, Ceil, Floor, RoundPreferFloor, PassThrough. See the Qt::HighDpiScaleFactorRoundingPolicy enum documentation for a full description of the options.

Paquet Windows de tests :
https://download.qelectrotech.org/qet/s … 1-04-17-1/

Je viens de faire quelques petits tests sur mon portable (écran UHD) et j'ai branché dessus un écran 1920x1080 sur le port HMI Windows affichage en mode étendu.

QET sur l’écran HMI

100% ok
125% pareil que toi, les bornes sont décalées, certains éléments débordent du cartouche.
150% ok
200% pas essayé

Il me semble avoir lu ici quelqu'un qui justement signalait un problème de rendu sur Win10 avec une mise à l’échelle justement de 125% avec un écran externe branché sur un portable.

andrea70ds wrote:

I solved my little problem , I changed resolution on left monitor , en fact on the left was 100 % and on PC right was 125% . In these case they must be the same .Thanks to Scorpio810 for suggestion .Many thanks .

https://qelectrotech.org/forum/viewtopic.php?id=1449

J'ai aussi fait le test de modification du script de démarrage mais ça n'a pas réglé le problème. Au passage, je n'ai pas vu de différence sur les polices...

Intéressant, merci.
Je testerai sans le "-platform windows:fontengine=freetype" plus tard, peut-être que chez Qt ils ont corrigé ce soucis depuis..
Pour information : le problème portait sur le rendu des polices textes des éléments affichés dans les folios.
https://qelectrotech.org/forum/viewtopi … 561#p10561

Merci pour ces renseignements qui ont le mérite pour la première fois d’être clair.
Un écran UHD dans le lot? style écran 4K sur le portable?