I have seen more and more programs getting packged in a way that the same file can be downloaded and run on most major distributions.  I was thinking if QET was available too like that it would ease adoption, and maybe less total work to reach more distros and wider audience?

It also makes it easy to have more than one version "installed" at the same time.
The frequent releases may not be needed in any other format, i think. (at least for Linux)

Example technical programs: For my 3dprinter i run FreeCAD and Slic3er as appimage, and there is KiCad from flatpack for circuit boards.  They are all packaged in my distro, but the flatpack & appimage from authors is updated to new versions quicker, and i can easily have both a stable reliable and a development version for new functions installed.

https://appimage.org/   https://www.flatpak.org/
They also have places they list available programs, so you could get marketing that way too nomicons/wink

My personal preference is Appimage as it do not need root privilegies to install appimages, and it is possible to run applications jailed easily if you are concerned about that.


BTW i tried to search forum first on this topic, but the search function here above only keep showing two instances of "Loading..." with Google Custom search logo between...

0.6 RC 4 have now been packaged in Mageia Linux development version "Cauldron", and will soon (weeks?) show up in current Mageia 6.  https://bugs.mageia.org/show_bug.cgi?id=20743

Thank you for the quick reply.
I did not enter this on my old install, so it then obviously used the old configuration file that was created at an installation.
Do we have a list of all things that can be set in the config file and command line for QETv0.6 ?

BTW one missed word in english translation: When it loads a drawing is displays a progress message saying i.e "23 sur 51" instead of "23 of 51"

Hi again.  Long time no see.
Have not been drawing anything for long time (mostly repairing things), but next week i will use your nice program again!
I read the thread on 0.7 and love the progress there, nice work nomicons/smile

0.7 seem too fresh for production use in my case, so i went for the latest 0.6
From 0.6 branch using svn i got revision 5223
I complied and run it using QtCreator.
System: Mageia Cauldron (development of Mageia 7), kernel 4.14.15, Qt 5.9.3, Plasma 5.11.95 running on X (not Wayland)
Machine: Thinkpad T400, dual core, Intel graphics, resolution 1280x800

I love the new icons, beautiful nomicons/smile

Quickly i see a couple problems, are they known? :

§1: Clicking menu Configuration -> Configurer QElectroTech:  The dialogue window is higher than screen, so OK and Cancel buttons are not visible.  Workaround: the window can not be resized by dragging it its corner or sides (why not?) but fortunately i can double click the frame to maximise it, or drag it to left or right to make it cover full height but half width of screen.  This is in Plasma, 800 px screen height.  Maybe better or worse on other desktops, and maybe worse on smaller screen?

§2: I can select language, and after close and restart it shows the new language in that dropdown, but menus are always still in French...

BTW, is there a way to make it auto-select system language at first launch?
First time the language select box is empty, so it can detect when it is not manually configured.

Thanks for thinking about it nomicons/smile

1) Data: QET like many other (but not all) design programs store used elements inside the design file, so no other data file should be necessary.

2) Program: there is never a guarantee that a later version of the design program can read a design file made with a many years earlier version.  So, please save a copy of the program installer the design was last saved with.  If you compile locally: all Qt thingys for that, and all sources of QET...

3) OS: Keep a install .iso or similar for the OS, and updates, and additions needed (Qt?)...

4) Hardware: keep hardware around many years (in this case for installing OS in case an emulator do not work)...  I recently had to borrow hardware to interface with a 30+ year controller from abroad...

Proprietary software often prohibits 2)&3), one reason libre software is much more reliable using.  4) may be a challenge after 30 years, it may be broken by age...

I do like that.  In your case i would make a master element that only contain the common part like power supply and communications interface.  And then slave element for the I/O ports.  (this is much like logic IC are commonly handled in electronic CAD: one symbol for power, and another symbol for the individual gates.  One difference is that those programs are built for it and handles it more elegantly)

Another case i have been experimenting with is to have a fluid valve as master, and as slaves to it i link the actuator (can be pneumatic or electric), and optionally also position sensor(s).  Very neat and tidy, avoids a lot of wiring mess.

58

(1 replies, posted in EN : Help, suggestions, discussions, ...)

You mean clickable links in pdf?
That is a feature request already nomicons/smile
https://qelectrotech.org/bugtracker/view.php?id=116

What is your screen resolution?

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.

I actually prefer manual saving, the hard time is to remember to do it...
My nomenclature is like this
[project]-[incremented number]-[optionally a short note of important changes since last].qet

For the time stamp i used to trust the filesystem, but that fail for most remote filesynchrinisation methods, so sometimes i note it after the incremented number.

(Yes i still exist, long time no see...) nomicons/smile

Welcome csz nomicons/smile

I am an occasional user and tester (mostly use Mageia Linux), but not a developer.

I start with two questions:

Are you using latest version from https://download.qelectrotech.org/qet/builds/nightly ?

Were you using the same version on W7?

scorpio810 wrote:
Nuri wrote:
scorpio810 wrote:

Windows XP is supported

still only by QElectroTech nomicons/grin

It's a little more work for me, but as long as it's possible for me, QElectroTech will support Windows XP for our users, and I think especially for those in education, schools and for all those in developing countries, or for those which not have money to buy a new machine or can't install Gnu/Linux and need to learn electricity, pneumatic, hydraulic, etc.. nomicons/smile

XP compatibility is great to have.
There are times you need XP for old programs needed by some old hardware in machines to service/rebuild, and it is good to be able to run QET on same system.  nomicons/smile

Thanks, will try later. Away for a week nomicons/smile

nomicons/smile

To set the defaults for new pages ("folios"), use Project properties.
Right click your project in the project list and select "Project properties" and select:

In the folio settings, remove the mark in the box next to "Visible text" in picture

Example from my laptop, texts overflowing.
(That page is a top plan of the PLC network of the equipment)

Ah great, and thanks for the quick reply nomicons/smile

Suggestion:

When issuing (like I did)

$ qelectrotech --help

it explain that option like:

  --config-dir=DIR              Definir le dossier de configuration

I dont know much french, but to me it looks like it say "Define configuration folder"

But QET still store configuration in ~.config/QElectroTech/QElectroTech.conf !

Instead it works like you say nomicons/smile  So please update the --help to reflect reality  nomicons/wink - that it defines the base dir of custom elements and title blocks

OR if you like, make that option really point to the configuration file, and make a new option
  --custom-dir=DIR    base folder of custom elements and title blocks

OR... was it meant that configuration file should be stored on the base folder of custom elements and title blocks?
(would also be nice if output in english if system language is not french, but most users guess the meaning anyway nomicons/smile )

On the laptop the screen is the same regardless if i boot windows or linux nomicons/wink  But i compiled QET locally on Linux with Qt 5.6.2
Compared to my workstation, on my laptop windows QET display texts smaller, but on Linux QET display texts *much* larger.

The text size on laptop in windows is close to size of what i see on workstation in Linux.


The windows QET is the "ready-to-use" development version.

My workstation have same Linux distro Mageia6, Plasma, and Qt versions as laptop, both use proprietary but different Nvidia drivers.

Laptop is an old Thinkpad T61p with 1600x1200 screen, workstation have 2560x1600.


From the link you gave I fail to distill a method to apply.  Maybe it got lost in google translation or i am just too tired.

To tell which system show the correct size, i guess i can make a text of large size "H" in element editor and measure how many dot high it is.    What would be correct measurement there?

Another test:
booting into MS Windows7 on that laptop and use the QET windows binary, the text is instead a little bit *smaller* than on my Mageia workstation.

There is another small problem: All text on schema is less beautiful - kerning and softness (i dont remenber the correct term right now) seem broken.  Menus and project list etc are all OK.

While not beautiful, it is good enough for my immediate need.

Picture left: Nice text in folio list - right: ugly rendered text on schematic

Maybe it is a question of what typefaces are installed?
I have only used default and not tred other.  Yet.

By command line or config file?
(makes syncing and multiboot easier)

I prepared my laptop to travel with the project to finish documentation on site.
To my horror i now see that all text in qet drawings are 50% larger there -> overlapping = unusable.
Also the pdf i export there show same problem.

I use exactly the same OS: Mageia 6, Plasma.

Any clue?

Ah you wanted to remove it.
Sorry I misunderstood.

Yes the default position of conductor labels most often make them land on the neighbour so unless moved manually the labeling is wrong.  (my drawings are pretty dense)

https://qelectrotech.org/bugtracker/view.php?id=91
https://qelectrotech.org/bugtracker/view.php?id=89

I often move them so they "sit" on the conductor