J'ai installé la version QET 0.9-dev (version installer) la semaine dernière sur la nouvelle workstation (DELL Precision I7 ) d'un collègue en Win 11 pro au boulot, ça fonctionne très bien.
https://www.dell.com/fr-fr/shop/station … 60mtwer_vp
Si tu as pris la ReadyToUse il faut cliquer sur le fichier "Lancer QET.bat " pour lancer QET.
2,026 2022-05-05 13:03:40
Re: Nouveautés de la version de développement 0.9 (236 replies, posted in News)
2,027 2022-05-05 08:23:40
Re: Nouveautés de la version de développement 0.9 (236 replies, posted in News)
Le filtre pour la position n 'est pas bonne en fonction du Label, il manque aussi de récupérer le numéro de fil lié à la borne..automatiquement.
https://download.qelectrotech.org/qet/f … er_dev.png
Le double click dans le champ de la xref d'une borne est une bonne idée, car il vient pointer la vue sur le schéma précisément sur cette borne.
Le calcul est très long même sur une grosse machine, une progressBar indiquerait l'avancement du calcul pour l'utilisateur.
2,028 2022-05-03 15:55:13
Re: change Textsize of multiple elements (5 replies, posted in EN : Help, suggestions, discussions, ...)
Hi,
open your project.qet file with a good text editor and change font size for selected texts, like kate on Linux.
2,029 2022-05-03 15:52:06
Re: Deux instance sur deux écrans (2 replies, posted in FR : Aide, suggestions, discussions, ...)
Salut Robert,
en principe non, mais ici sur ma Debian j'y arrive, je lance QET sur mon premier écran puis je lance une AppImage pour avoir une autre instance de QET sur l'autre écran.
J'avais au départ pensé que passer sur des fenêtres pour les projets au lieu des onglets réglerait le problème, en fait non!
Si tu est sur Windows, tu peux essayer avec la version installer et ensuite en lançant la version ReadytoUse
Deux 27 P screens one is an UHD other is QHD
Screen capture on my setup with 2 scrrens:
*** Qt screens ***
( 1 : 3840 x 2160 )
( 2 : 1920 x 1080 ) 
2,030 2022-05-02 06:36:24
Re: I get the drawing "in my face" when i double click referencing... :) (40 replies, posted in EN : Help, suggestions, discussions, ...)
Morganol wrote:
Sorry for late reply.
No, my simple idea is not to export it using another program, and maybe not making changes in QET either.The simple idea is that by making QET printing links so they visually looks like links, then i guess it is relatively simple to create a small separate program that parse the pdf and rewrites the links so they actually work like links.
Example: if i in xref and folio referencing settings fields put %F@%f%l%c,
then i will for folio "Pump", page 2, coordinate C7 get: Pump@2C7If i enter such formatting in my example drawing from my post https://qelectrotech.org/forum/viewtopi … 5577#p5577 , it looks like the following screen-shot, and it also displays like that when opening the exported pdf.
Now if we had a small program that can process that pdf and make the links coma alive it would be great. the only thin i want it to do is find the number between the @ and a following alphabetical character and make a link of that to the page of that number.
OK the above is simplified, to make it work reliably we probably need a more reliable trigger than a one character "@"....
But we do not want a long trigger string to be shown at link in normal shema in QET nor printing to printer from QET.Having no idea how QET works, i can just say maybe it can temporarily automatically append "LINKME@" plus page number to every xref and folio ref formula just when printing to pdf.
The external program then scans for "LINKME@" and read the page number after it to create the link target, and remove "LINKME@" and the number from the visual part.
That will be compatible with any form of ref formula the user have chosen.
Except, user can nowhere write "LINKME@" but that is very little chance...Maybe the external program, could even be an integrated part of QET, run automatically directly after initial file is exported, or even streamed so the first version of pdf never is externally written out.
Add Internal link with QET advanced text editor like <a href="#page=10"> work weel but you need only to open this PDF document with Google Chrome,
example with invisible text for link #page=10 on page 100 to go to page 10
<html><head/><body><p><a href="#page=10"><span style=" font-family:'Sans Serif'; font-size:9pt; text-decoration: underline; color:transparent;">10</span></a></p></body></html>A possible hack is to use python library to open an PDF file generated by QET .. https://pythonguides.com/pdffilewriter-python-examples/
https://stackoverflow.com/questions/633 … ink-to-pdf
https://stackoverflow.com/questions/287 … nks-in-pdf
Link annotations in PDF documents are associated with a geometric region of a page rather than a particular object in a content stream. For this reason, link annotations alone are not useful for users with visual impairments, or to applications that must determine which content can be activated to invoke a hypertext link.
Tagged PDF /Link elements use PDF's logical structure to establish the association between content items and link annotations, providing functionality comparable to HTML hypertext links.
In HTML, the following example produces text containing a hypertext link:
Here is some text <a href="https://www.w3.org/WAI/"> with a link </a> inside.
In PDF the page must be painted first and then a link annotation placed over the area where the object action will occur.
The following code fragment shows PDF equivalent to the HTML above; it uses link text displayed in blue and underlined. A second code fragment follows, indicating the associated logical structure hierarchy. This is typically accomplished by an authoring tool.
/P <</MCID 0>> %Marked Content Sequence 0 (paragraph)
BDC %Begin marked content sequence
BT %Begin text object
/F1 11.04 Tf %set text font and size
1 0 0 1 72.024 709.54 Tm %set text matrix
0 g %set non stroking color to black
0 G %set stroke color to black
[(H)3(ere )-4(is s)10(o)5(m)-4(e)9( t)-3(e)9(xt)-3( )] TJ %Show text preceding the link" Here is some text"
ET %end text object
EMC %end marked content sequence
/Span <</MCID 1>> %Marked Content Sequence 1 (underlined link text)
BDC %Begin marked content sequence
BT %Begin text object
1 0 0 1 152.42 709.54 Tm %set text matrix
0 0 1 rg %set non-stroking color to blue
0 0 1 RG %set stroke color to blue
[(with a )-2(li)3(n)14(k)] TJ %Show link text " with a link"
ET %end text object
0 0 1 rg %set stroke color to blue
152.42 707.62 45.984 0.72 re %rectangle operator - target area for the link
f* %fill the path using the even-odd rule
EMC %end marked content sequence
/P <</MCID 2>> %Marked Content Sequence 2 (paragraph)
BDC %Begin marked content sequence
BT %begin text object
1 0 0 1 198.41 709.54 Tm %set text matrix
0 g %set non stroking color to black
0 G %set stroke color to black
[( )] TJ %empty text string showing white space
ET %end text object
BT %begin text object
1 0 0 1 200.93 709.54 Tm %set text matrix
[(in)5(sid)5(e.)] TJ %show text following the link "inside."
ET %end text
BT %begin text object
1 0 0 1 229.97 709.54 Tm %set text matrix
[( )] TJ %empty text string showing white space
ET %end text object
EMC %end marked content sequence
The following code fragment is an excerpt from the logical structure that establishes the association between the content items and the link annotation:
11 0 obj %Object ID 11, generation 0, obj keyword
<</K[1 %immediate child of the structure tree root
<<
/Obj 26 0 R %reference to Object 26
/Type/OBJR %this object describes an indirect object reference
>>]
/P 12 0 R
/Pg 17 0 R
/S/Link
>>
endobj
26 0 obj %object ID 26 which is referenced by the OBJR in Object 11
<</A 31 0 R
/BS
<</S/S
/Type/Border
/W 0
>>
/Border[0 0 0] %a colorless border
/H/I
/Rect[150.128 694.558 200.551 720.0] %the boundaries defining target area where link annotation is active
/StructParent 1
/Type/Annot %Structure element is an annotation
/Subtype/Link
>> %It is a link annotation
endobj
31 0 obj %Object 31, gen 0, obj
<</S/URI %Object type is URI action
/URI(https://www.w3.org/WAI) %The Uniform resource identifier to resolve
>>
endobj
2,031 2022-05-01 11:55:04
Re: qelectrotech language and project language (3 replies, posted in EN : Help, suggestions, discussions, ...)
Hi vilatech,
for now you can't.
But I think now a workaround is possible : qet_en.qm is translation binary English for UI.
Copy this file and rename it by example to country you want like qet_nl.qm and of course delete old file or backup it to other directory.
Launch QET and select now Nederlands flags, restart QET.
2,032 2022-04-30 11:59:26
Re: qelectrotech language and project language (3 replies, posted in EN : Help, suggestions, discussions, ...)
Hi,
maybe you could help to translate, is easy, see:
https://qelectrotech.org/wiki_new/doc/translation
https://doc.qt.io/qt-5/linguist-translators.html
Because word chain's to translate are in French in the code you need:
https://doc.qt.io/qt-5/linguist-transla … ltaneously
2,033 2022-04-29 18:16:26
Re: cntrl + not working in last linux update - Date : Apr 25 2022 : 16:49: (12 replies, posted in EN : Help, suggestions, discussions, ...)
Thanks for your feedback.
2,034 2022-04-29 18:11:58
Re: Nouveautés de la version de développement 0.9 (236 replies, posted in News)
I'm thinking of buying a certificate to sign Windows and maybe for macOS packages.?... and using osslsigncode to sign Windows packages, what do you think?
It would cost about ~ 130€ with shipping for the first year for certicate and an USB key encrypted, then 25€/year to renew the certificate.
We can afford to pay for it now thanks to your Paypal donations, but before I go ahead I'd like your opinion, for those who have tested it?
As you know, under Windows and macOS the installation of QET is painful with workarounds for mac and warning messages from Windows during installation.
https://shop.certum.eu/open-source-code-signing.html
https://github.com/mtrojnar/osslsigncode
https://www.msz.it/a-cheap-code-signing … lkthrough/
EDIT:
Open Source Code Signing Certificate
We issue Open Source Code Signing certificates only to natural persons.
We would like to inform you that since March 13, 2017, the option of telephone verification for Open Source Code Signing certificates is not available.
Verification based on documentsCopies of the following documents must be provided to Certum for verification purposes:
confirmation of identity at the Registration Point or at the Identity Confirmation Point (details: https://certum.store/certum-reseller-points-map, sample statement can be downloaded here (link: https://files.certum.eu/documents/repsi … ntity.pdf) or
notarized proof of identity or for quicker issuance
a copy of the identity document of the person requesting the certificate (identity card, passport, driver’s license, permanent residence card).
ATTENTION! The copy should be a complete reproduction of the document (i.e. include all of its pages).The identity can also be confirmed on the basis of a valid qualified certificate issued for the Subscriber by Certum.
anda utilities (gas, electricity, water, telephone, etc.) bill issued to the subscriber,
the website address of the ongoing Open Source project.
The project must be publicly available and indicate clearly the subscriber’s relationship with the project. If Certum is unable to identify the project based on publicly available information, the certification application will be rejected.
All collected documents should be sent to Certum using one of the following methods:by e-mail as a password-protected file to the address: ccp@certum.pl (recommended form),
please contact the Certum technical support helpline in order to determine how to transfer the password
by fax to: +48 91 4257 422
by post to:
Asseco Data Systems S.A.
ul. Bajeczna 13
71-838 Szczecin
NOTE
1. Open Source Code Signing certificates cannot contain domain names and IP addresses.
2. The person requesting the certificate must also be the certificate subscriber.
3. We issue Open Source Code Signing certificates only to natural persons.
4. When a certificate is issued, the phrase “Open Source Developer” is automatically added in the “CN” (Common Name) field, while the Organization field only contains “Open Source Developer”.NOTE!
Validity of the documents being the basis for verification of certification applications:For new certificate requests and for renewed certificates, documents and information from public registers cannot be older than 13 months,
Authorization documents, whether they are timely or not – remain valid for 13 months from the date of issue,
Identity documents must be up-to-date (valid) on the day the certificate is issued.
Identity documents delivered to Certum should be e-mailed in the form of a password-protected file, please contact the Certum technical support helpline in order to determine how to transfer the password
Well, WTF ...... ! 
2,035 2022-04-28 21:45:24
Re: Text on text problem (3 replies, posted in EN : Help, suggestions, discussions, ...)
Check for other type : coil, organ of protection, switch / button
You can define where XRefs text that are displayed following the type.
On your capture type is for coil, K1 contact is the slave of K1 coil.
2,036 2022-04-28 14:14:00
Re: qet_translate (16 replies, posted in Elements)
Also added to our repository on the servers:
https://download.qelectrotech.org/qet/b … translate/
Edit : added description and links on main download page:
https://qelectrotech.org/download.html.en
Hello Vbxler,
maybe if you send me sources files and how to compile it, I can try to build a macOS bundle or executable.
https://wiki.freepascal.org/Portal:Mac
https://wiki.freepascal.org/Installing_Lazarus_on_macOS
http://www.ipst-info.net/LinuxJournal/LJ/185/10502.html
2,038 2022-04-28 13:29:43
Re: qet_translate (16 replies, posted in Elements)
Nice work, thanks Vbxler. ;-)
2,039 2022-04-26 18:52:41
Re: qet_translate (16 replies, posted in Elements)
ps: When the definition of the tag name is the same in several languages, it is not useful to add other flags, as "en" works for all languages if it is the only tag.
+ <names>
+ <name lang="ru">flb3205_gsm</name>
+ <name lang="pl">flb3205_gsm</name>
+ <name lang="nb">flb3205_gsm</name>
+ <name lang="sr">flb3205_gsm</name>
+ <name lang="en">flb3205_gsm</name>
+ <name lang="el">flb3205_gsm</name>
+ <name lang="es">flb3205_gsm</name>
+ <name lang="ja">flb3205_gsm</name>
+ <name lang="nl">flb3205_gsm</name>
+ <name lang="fr">flb3205_gsm</name>
+ <name lang="ro">flb3205_gsm</name>
+ <name lang="de">flb3205_gsm</name>
+ <name lang="pt">flb3205_gsm</name>
+ <name lang="it">flb3205_gsm</name>
+ <name lang="cs">flb3205_gsm</name>
+ <name lang="ar">flb3205_gsm</name>
+ <name lang="hr">flb3205_gsm</name>
+ <name lang="da">flb3205_gsm</name>
+ <name lang="sl">flb3205_gsm</name>
+ <name lang="ca">flb3205_gsm</name>
+ <name lang="be">flb3205_gsm</name>
+ <name lang="tr">flb3205_gsm</name>
+ <name lang="hu">flb3205_gsm</name>
+ <name lang="mn">flb3205_gsm</name>
+ </names>
+ <elementInformations>
Prefer :
<names>
<name lang="en">flb3205_gsm</name>
</names>
<elementInformations>
2,040 2022-04-26 16:26:44
Re: cntrl + not working in last linux update - Date : Apr 25 2022 : 16:49: (12 replies, posted in EN : Help, suggestions, discussions, ...)
Select gesture for touchpad
https://download.qelectrotech.org/qet/m … rance.html
Keyboard movements
https://download.qelectrotech.org/qet/m … _grid.html
2,041 2022-04-26 16:20:49
Re: cntrl + not working in last linux update - Date : Apr 25 2022 : 16:49: (12 replies, posted in EN : Help, suggestions, discussions, ...)
For zoom in/out you could use keyboard ctrl + +/- keys, and or mouse roller, or multi-gesture on your touchpad (Pinch-to-zoom, etc ..) if you enable it in config.
2,042 2022-04-26 16:15:26
Re: cntrl + not working in last linux update - Date : Apr 25 2022 : 16:49: (12 replies, posted in EN : Help, suggestions, discussions, ...)
Select 4 AT Translated Set 2 keyboard
2,044 2022-04-26 15:37:58
Re: cntrl + not working in last linux update - Date : Apr 25 2022 : 16:49: (12 replies, posted in EN : Help, suggestions, discussions, ...)
Hi,
you could try with sudo evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0: Logitech K540/K545
/dev/input/event1: Logitech M510
/dev/input/event2: Generic USB Audio Consumer Control
/dev/input/event3: Generic USB Audio
/dev/input/event4: MSI MYSTIC LIGHT
/dev/input/event5: Power Button
/dev/input/event6: Power Button
/dev/input/event7: PC Speaker
/dev/input/event8: HDA ATI HDMI HDMI/DP,pcm=3
/dev/input/event9: HDA ATI HDMI HDMI/DP,pcm=7
/dev/input/event10: HDA ATI HDMI HDMI/DP,pcm=8
/dev/input/event11: HDA ATI HDMI HDMI/DP,pcm=9
/dev/input/event12: HDA ATI HDMI HDMI/DP,pcm=10
Select the device event number [0-12]: 0
Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0x46d product 0x4076 version 0x111
Input device name: "Logitech K540/K545"
Testing ... (interrupt to exit)
Event: time 1650980111.940440, type 17 (EV_LED), code 0 (LED_NUML), value 0
Event: time 1650980111.940440, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70028
Event: time 1650980111.940440, type 1 (EV_KEY), code 28 (KEY_ENTER), value 0
Event: time 1650980111.940440, -------------- SYN_REPORT ------------
Event: time 1650980115.204108, type 4 (EV_MSC), code 4 (MSC_SCAN), value 700e0
Event: time 1650980115.204108, type 1 (EV_KEY), code 29 (KEY_LEFTCTRL), value 1
Event: time 1650980115.204108, -------------- SYN_REPORT ------------
Event: time 1650980115.372100, type 4 (EV_MSC), code 4 (MSC_SCAN), value 700e0
Event: time 1650980115.372100, type 1 (EV_KEY), code 29 (KEY_LEFTCTRL), value 0
Event: time 1650980115.372100, -------------- SYN_REPORT ------------
Event: time 1650980119.741677, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70057
Event: time 1650980119.741677, type 1 (EV_KEY), code 78 (KEY_KPPLUS), value 1
Event: time 1650980119.741677, -------------- SYN_REPORT ------------
+Event: time 1650980119.827671, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70057
Event: time 1650980119.827671, type 1 (EV_KEY), code 78 (KEY_KPPLUS), value 0
Event: time 1650980119.827671, -------------- SYN_REPORT ------------
Event: time 1650980127.310971, type 4 (EV_MSC), code 4 (MSC_SCAN), value 700e0
Event: time 1650980127.310971, type 1 (EV_KEY), code 29 (KEY_LEFTCTRL), value 1
Event: time 1650980127.310971, -------------- SYN_REPORT ------------
Event: time 1650980127.578685, type 1 (EV_KEY), code 29 (KEY_LEFTCTRL), value 2
Event: time 1650980127.578685, -------------- SYN_REPORT ------------
Event: time 1650980127.618684, type 1 (EV_KEY), code 29 (KEY_LEFTCTRL), value 2
Event: time 1650980127.618684, -------------- SYN_REPORT ------------
Event: time 1650980127.658684, type 1 (EV_KEY), code 29 (KEY_LEFTCTRL), value 2
Event: time 1650980127.658684, -------------- SYN_REPORT ------------
Event: time 1650980127.698686, type 1 (EV_KEY), code 29 (KEY_LEFTCTRL), value 2
Event: time 1650980127.698686, -------------- SYN_REPORT ------------
-Event: time 1650980334.123792, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70056
Event: time 1650980334.123792, type 1 (EV_KEY), code 74 (KEY_KPMINUS), value 0
Event: time 1650980334.123792, -------------- SYN_REPORT ------------
2,045 2022-04-26 15:26:25
Re: Ewon Flexy 205 (5 replies, posted in Elements)
Hi Vbxler,
done, thanks.
2,047 2022-04-26 10:37:08
Re: qet_translate (16 replies, posted in Elements)
The dialog for saving the qet_directory file always returns where the program is installed.
A workaround is to place the executable in the git working directory.
cat qet_translate.ini
[qet_cad]
elements=/home/laurent/Qet-svn/git/qet/elements
2,048 2022-04-26 10:06:21
Re: qet_translate (16 replies, posted in Elements)
I tried qet_translate_linux64, it 's work great, thanks.
For translation, select source language to English is better than French.
Example French bobine :
<name lang="ar">بكرة</name>
<name lang="ca">rodet</name>
<name lang="cs">role</name>
<name lang="da">rulle</name>
<name lang="de">Spule</name>
<name lang="el">καρούλι</name>
<name lang="en">reel</name>
<name lang="es">carrete</name>
<name lang="fr">bobine</name>
<name lang="hr">kolut</name>
<name lang="hu">orsó</name>
<name lang="it">bobina</name>
<name lang="ja">リール</name>
<name lang="mn">ороомог</name>
<name lang="nb">hjul</name>
<name lang="nl">haspel</name>
<name lang="pl">rolka</name>
<name lang="pt">carretel</name>
<name lang="pt_br">carretel</name>
<name lang="ro">tambur</name>
<name lang="ru">катушка</name>
<name lang="sl">kolut</name>
<name lang="sr">колут</name>
<name lang="tr">makara</name>
English coil :
<name lang="ar">لفه</name>
<name lang="ca">bobina</name>
<name lang="cs">cívka</name>
<name lang="da">spole</name>
<name lang="de">Spule</name>
<name lang="el">σπείρα</name>
<name lang="en">coil</name>
<name lang="es">bobina</name>
<name lang="fr">bobine</name>
<name lang="hr">zavojnica</name>
<name lang="hu">tekercs</name>
<name lang="it">bobina</name>
<name lang="ja">コイル</name>
<name lang="mn">ороомог</name>
<name lang="nb">Spole</name>
<name lang="nl">spoel</name>
<name lang="pl">cewka</name>
<name lang="pt">bobina</name>
<name lang="pt_br">bobina</name>
<name lang="ro">bobina</name>
<name lang="ru">катушка</name>
<name lang="sl">tuljava</name>
<name lang="sr">калем</name>
<name lang="tr">bobin</name>
2,049 2022-04-26 06:52:03
Re: cntrl + not working in last linux update - Date : Apr 25 2022 : 16:49: (12 replies, posted in EN : Help, suggestions, discussions, ...)
Strange! ctrl +/- work here on my Debian Sid with
QElectroTech V 0.90-DEV+17290ae3bb0a58100c957a06d79751d3
Compilation : GCC 11.2.0
Built with Qt 5.15.2 - Date : Apr 25 2022 : 16:44:31
Run with Qt 5.15.2 using 48 thread(s)
CPU : model name : AMD Ryzen Threadripper 3960X 24-Core Processor
RAM Total : 64257 MB
RAM Available : 59532 MB
GPU : Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 540X/550/550X] (rev c7)
GPU RAM : Video memory: 4096MB Dedicated video memory: 4096 MB Currently available dedicated video memory: 3086 MB
OS : linux - x86_64 - Version : Debian GNU/Linux bookworm/sid - Kernel : 5.17.4-vanilla
*** Qt screens ***
( 1 : 3840 x 2160 )
( 2 : 1920 x 1080 )
2,050 2022-04-24 19:24:06
Re: QElectroTech howto found on the WWW (53 replies, posted in Videos howto)
Nice Car electrical wiring
https://download.qelectrotech.org/qet/s … iagram.pdf