You are not logged in. Please login or register.
Active topics Unanswered topics
Search options (Page 205 of 299)
https://qelectrotech.org/forum/viewtopi … 5323#p5323
scorpio810 wrote:Pendant l'installation il te propose d'ajouter l’exécutable dans le path, il faut cocher l'option, ça évite d’avoir à écrire son chemin à chaque fois.
Ou d’éditer les variables d’environnement par la suite pour ajouter son chemin.
Thank you. 
If you know someone for this job?
Bonjour,
oui tout à fait et l'immense majorité dessine dessus, on devrait la releaser bientôt, c'est juste que je n'ai pas le temps en ce moment d’écrire le big changelog, sinon elle serait déjà sortie.
Bonjour,
tu as bien la dernière version de QET 0.6 RC..?
L'entrée dans le menu projet a rajoutée que récemment sur la version 06- dev, donc tu ne la trouveras pas sur une vielle version 0.5 ou 0.4.
Sur la 0.5 le plugin python de Raul devrait fonctionner, mais en le lançant directement.
Si tu as des questions sur l'installation du plugin n’hésite surtout pas.
Si le plugin n'est pas installé, alors la procédure d'installation s'affiche, sinon le générateur de bornier ce lance.
je pense que, en attendant, ce n'est pas une implémentation très compliquée à réaliser
Tu te trompes, c'est deux méthodes complètement différentes de navigation dans le projet.
De mémoire, je pense que ce n'est pas si simple que tu as l'air de le mentionner.
Merci de nous le rappeler, on l'avait oublié celui là ...
Mais pour l'instant, nous n’avons pas encore trouvé le pourquoi de ce problème, ni trop cherché aussi, autant le dire. 
In the past, I have added HTML support for elements text like edit text field in diagram, I can change element text size, element color text directly in diagram, etc, but I reverted this !
Why ?
this addon increase size of a QET project X 10, and I do not want it.
Example :
<inputs>
<input y="303.282" x="464.885" text="<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd">
<html><head><meta name="qrichtext" content="1" /><style type="text/css">
p, li { white-space: pre-wrap; }
</style></head><body style=" font-family:'Sans Serif'; font-size:9pt; font-weight:400; font-style:normal;">
<p style=" margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px;"><span style=" font-family:'Noto Sans'; font-size:14pt; font-weight:600; text-decoration: underline;">test</span></p></body></html>"/>
</inputs>
Hi,
minors fix and new builds here :
https://download.qelectrotech.org/qet/b … 017-05-27/
Edit : added MacOS build DXFtoQET.app.zip
Enjoy !
Hi,
I build new version for Windows 32/64 bits (Qt 5.8) and Gnu/linux (Qt 5.7.1 X86_64).
https://download.qelectrotech.org/qet/b … 017-05-25/
unio wrote:scorpio810 wrote:It' s 4965 version?
I rebooted the computer and now 4965 version print correctly on any size screen. Thank you!
Nice, new Windows build is for soon 4966.
You could try if is always ok?
But why do I have the correct print QT version 5.5.1 and can I somehow configure the QT version 5.8.0 for correct printing?
It 's more complicated : see Qt manual
https://qelectrotech.org/forum/viewtopi … 6591#p6591
1) we don't have HDPI monitors.
2) If we have this monitors we need to try and check it in a real install not in virtual machine.
3) I don't want to install Windows in hard here, and not time and not the envy to try a install real hackintosh in my PC.
I have already spent a lot of time to run my old virtual machine Yosemite hackinstosh in this new Ryzen hardware.
I just returned the function Qt::AA_EnableHighDpiScaling for macos in 4966 commit.Someone can try new builds?
Thank you.
Nice, by default with 100% scaling it 's ok.
It' s 4965 version?
Put your video link into quote HTML tag
@ Unio : u can try latest 4965 packages?
Same for Morganol ! ;-)
cubero wrote:I've upgraded right now and version 0.60.r4962 works properly.
Thanks
Ok, thank you.
I 'll commit changes and build Windows packages, for Windows users can try.
Morganol wrote:OK for me on Qt 5.6.2, Mageia 6
EDIT: QET rev 4964 locally compiled in Qt Creator run in debug mode) screen res 2560x1600 /EDIT
To me it looks like on unio's system:
The conductors seem to go to correct drawing coordinates? (no ofset)
The elements are double size! I beleive they have correct insetion point, which varies by element. Example: i think the computer element have insertion point defined top left if my theory is correct.
Weird.
You could try r4963?
svn export svn://svn.tuxfamily.org/svnroot/qet/qet/trunk --revision 4963 qelectrotech_trunk_4963
Or use
svn patch r4962-scorpio810.diff
You could try latest svn ubuntu packages?
https://launchpad.net/~scorpio/+archive/ubuntu/ppa
0.60.r4962
I reverted it after.
-#if (QT_VERSION >= QT_VERSION_CHECK(5, 6, 0))
-QCoreApplication::setAttribute(Qt::AA_EnableHighDpiScaling);
-#endif
+#if QT_VERSION >= QT_VERSION_CHECK(5,6,0)
+ QApplication::setAttribute(Qt::AA_DisableHighDpiScaling);
+#else
+ qputenv("QT_DEVICE_PIXEL_RATIO", QByteArray("1"));
+#endif // QT_VERSION
return(QETApp(argc, argv).exec());
}
No problem here :
Debian Qt 5.7.1
Win 10 Qt 5.8
https://vicrucann.github.io/tutorials/osg-qt-high-dpi/
But :
An experimental implementation of high-DPI scaling was introduced in Qt 5.4. It was enabled by the environment variable QT_DEVICE_PIXEL_RATIO, which could be set to a numerical scale factor or "auto". This variable is deprecated in Qt 5.6.
http://doc.qt.io/qt-5/highdpi.html
In order to get an application designed for low DPI values running on a high resolution monitors quickly, consider one of the scaling options (let the application run as DPI Unaware on Windows or set the environment variable QT_AUTO_SCREEN_SCALE_FACTOR to "1". These options may incur some scaling or painting artifacts, though.
In the longer term, the application should be adapted to run unmodified:
Always use the qreal versions of the QPainter drawing API.
Size windows and dialogs in relation to the screen size.
Replace hard-coded sizes in layouts and drawing code by values calculated from font metrics or screen size.
Posts found: 5,101 to 5,125 of 7,463
Generated in 0.112 seconds (18% PHP - 82% DB) with 5 queries
