Search options (Page 14 of 300)

by

source venv/bin/activate

(venv) [14:20:26] laurent@debian:~$ whereis qet_tb_generator 
qet_tb_generator: /home/laurent/venv/bin/qet_tb_generator
(venv) [14:27:18] laurent@debian:~$ 

Now in the same terminal launch QET

qelectrotech

Example here
(venv) [14:20:26] laurent@debian:~$ qelectrotech

14:19:59.059 Info:  project to use for qet_tb_generator:  "/home/laurent/Qet-svn/git/qet/examples/industrial.qet" 
14:19:59.059 Info:  success so far:  false   - now searching for  "/home/laurent/.local/share/QElectroTech/QElectroTech/binary/qet_tb_generator" 
14:19:59.059 Info:  success so far:  false   - now searching for  "/home/laurent/qet_tb_generator" 
14:19:59.059 Info:  success so far:  false   - now searching for  "/home/laurent/.qet/qet_tb_generator" 
14:19:59.059 Info:  success so far:  false   - now searching for  "/home/laurent/venv/bin/qet_tb_generator" 
14:19:59.091 Info:  success so far:  true   - now searching for  "qet_tb_generator" 
14:19:59 INFO     QET Terminal Block Generator - v1.3.1 [main.main:840]

Maybe edit QET launcher to ?

source venv/bin/activate && qelectrotech %F

grep ^processor /proc/cpuinfo | wc -l
48

I don't have 48 cores only Hyper-Threading Technology!
24 cores = 48 threads for this CPU.
Setup AMD   3960X it's very very old now but compile quickly still QET in 28 seconds. 150W en idle...   ~600 W when I use all cores ... like make -j 48.
I think the new mainstream AMD hardware performs better... for less power...

It's very usefull like build all tool-chain cross-compilation like MXE env, instead of the machine compiling continuously in 8 hours, it's done in about 1 hour.

Hallo plc-user,

"qet_tb_plugin" isn't easy to found:
On Windows you can make a binary.exe but all antirus refuse them...
https://qelectrotech.org/forum/viewtopi … 141#p17141
https://qelectrotech.org/forum/viewtopi … 150#p17150

Now it's more complicated under Debian like, they require you to install python in a virtual venv, see:
https://qelectrotech.org/forum/viewtopic.php?id=2861

Edit: https://qelectrotech.org/forum/viewtopi … 640#p20640

Hallo plc-user and thanks,

merged and package it for Debian, Ubuntu PPA, windows, please could you check-it?

No news about Joshua since november 2024. The delicate operation on his partner's severely damaged vertebrae went well and she is gradually recovering.

I was slow to reply, but I haven't heard from her since.

I hope he'll read this. And that they're well.

Best regards,
Laurent

Hallo plc-user,

i just published all packages, please try and check.
I don't publish arm64 macOS at this time. maybe this week...

Thanks,
Laurent

2)

Hi plc-user and thanks for your little manual for the transition,
I will try to do it for macOS, maybe next week if I have time,
but I have to install a new macOS VM on my mac Mini and install december QET and compare the old locations with new QET  version's files PATH . But if someone can do it, I'd be relieved

Strange, again?
see --> Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details

https://qelectrotech.org/wiki_new/doc/i … or_details

Hallo plc-user,

I can't remember, I think it's been from the beginning...
I've always hated DesktopLocation... which saves the default project under Desktop! So I prefer to "save it" to others PATH.

Change can be easy, like this:

--- sources/qetproject.cpp
+++ sources/qetproject.cpp
@@ -369,7 +369,7 @@ QString QETProject::currentDir() const
 {
     QString current_directory;
     if (m_file_path.isEmpty()) {
-        current_directory = QStandardPaths::writableLocation(QStandardPaths::DesktopLocation);
+        current_directory = QStandardPaths::writableLocation(QStandardPaths::DocumentsLocation);
     } else {
         current_directory = QFileInfo(m_file_path).absoluteDir().absolutePath();
     }

Best regards
laurent

Edit :

https://github.com/qelectrotech/qelectr … 4db6af63a1

And

https://github.com/qelectrotech/qelectr … e1a08775fa

Hallo plc-user,

As expected, things aren't going so well

Um, Maybe I think I made a a little mistake when merging your PR, there are a lot of things to re-set,like elements, ect locations PATH, the location of binary plugin collections, the path in the logs now was  wrong, and so on.

DXF2elmt Binary or QETelementScaler offers me this PATH now on my Debian: /home/laurent/.local/share/QElectroTech/QElectroTech/binary/

Sometimes you have to demolish everything in order to rebuild better.

Best regards,
Laurent