Could you also make a 0.61 Appmiage ?
On KDE5 Plasma:
(All names guessed from translating from Swedish)
Plasma settings > Appearance > Font > Font
[x] Force font dots per inch:
Higher number will make all text bigger in menues, dialogs, drawing.
The QET drawing template editor have check boxes to make the text size automatically limit to available space.
I love how you guys develop this program!
Hi and welcome to the forum
You mean it simply vanishes from the screen?
When do that happen?
Which version of QET do you run?
Try to launch it from a terminal and see if you get any interesting messages.
You could try if the appimage works.
You could use the arrows found in
Close to the title block on all pages draw a short line and use the arrows, and link to adjacent pages.
I use a similar method but link to and from block schematic page(s), using home brew symbols instead of the arrows.
Can you tell us a bit of what system you use?
If you start it from command line, is there any messages when it crashes?
Edit: Oh by the way:
Welcome to the club
Thanks. I am sure it if of interest to many. Maybe you could even put such procedures on the wiki?
Myself is on a kind of computer diet period. Instead, i do much mechanic work and practical watering, hands-on-controls repair, repairing a tractor and such things currently.
1) Maybe you could copy or link that informations at the appimage download page? (and later in some manual...) plus a link to https://appimage.org/ where users can learn about appimage, how to run it, and they may want to use firejail.
2) I see you have added appimage links to 0.6 and 0.7 versions at https://qelectrotech.org/download.html . You can also add one for 0.5.
3) Now you can get the news out and attract more users by getting it listed where Appimages are listed. I know of https://bintray.com/probono/AppImages , https://appimage.github.io/apps/ , maybe there are more places.
Great! I put the news here https://wiki.mageia.org/en/QElectroTech#Appimage and also noted it in the forum recently
0.5 and 0.6 launch cleanly. 0.5 complains in the terminal of symbols saved with later version, as expected.
Is it possible to launch the appimages with some parameter or other trick to make them use different folders of symbols, templates, drawings?
Same simple test, same OK result
Launches cleanly, seem to work correctly (very quick test) and exits cleanly without segfault (Mageia 6, Plasma).
$ ./QElectroTech_-x86_64.AppImage ./qelectrotech: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by /tmp/.mount_QElectz2Esmr/usr/bin/../lib/libQt5Core.so.5) bash-4.3$
I it possible to include more in the appimage to make it less system dependent?
Previous version worked OK per comment 9, and this is output in terminal from where it was launched and then closed:
bash-4.3$ ./QElectroTech_-0.70.r5428.glibc2.14-x86_64.AppImage /home/morgan/.local/share/applications/appimagekit-qelectrotech.desktop: warning: value "Editor výkresů elektrických obvodů" for key "Comment[cs]" in group "Desktop Entry" looks redundant with value "Editor výkresů elektrických obvodů" of key "GenericName[cs]" QSqlDatabase: QSQLITE driver not loaded QSqlDatabase: available drivers: Unable to open the SQLite database "/home/morgan/.qet//elements_cache.sqlite" as "ElementsCollectionCache-0" : QSqlError("", "Driver not loaded", "Driver not loaded") Segmenteringsfel (minnesutskrift skapad) bash-4.3$
I dont know the impact of the sql problems; did not notice any usage problems but did not try everything.
The new version fail to launch; after the dialog about wether to integrate this appimage in the system, it exits, and this is found in the terminal:
bash-4.3$ ./QElectroTech_-0.70.r5435.glibc2.14-x86_64.AppImage /home/morgan/.local/share/applications/appimagekit-qelectrotech.desktop: warning: value "Editor výkresů elektrických obvodů" for key "Comment[cs]" in group "Desktop Entry" looks redundant with value "Editor výkresů elektrických obvodů" of key "GenericName[cs]" gtk-update-icon-cache: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by /tmp/.mount_QElectDf2G3F/lib/x86_64-linux-gnu/libmount.so.1) gtk-update-icon-cache: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by /tmp/.mount_QElectDf2G3F/lib/x86_64-linux-gnu/libblkid.so.1) /tmp/.mount_QElectDf2G3F/usr/bin/qelectrotech: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by /tmp/.mount_QElectDf2G3F/lib/x86_64-linux-gnu/libbsd.so.0) bash-4.3$
I have glibc 2.22 installed.
It seem to just work on Mageia 6. Only tested a few minutes so far: new shema, opening a 0.6 version shema and editing it, save, close, reopen. Print to physical printer, print to pdf. It seem to use configuration from already installed 0.6 version: project folder, history, user collection.
Noticed the old issue that floating tool bars appear on every desktop. I use Plasma 5.12 with 3x3 desktops. Qt5.9.4.
A minor language quirk: When opening a project there is the dialogue:
"Opening of the project..."
Remove "of " so it becomes: "Opening the project..."
BTW i think it is a good idea to provide checksums.
When exiting, it throws segmentation fault.
Yes, as I said "Did i have money", i dont have more then needed to get around, since i "went into the wall".
I bought my monitor used years ago. Was impressive then with 30" 2560x1600, displayport. I also still use the machine i built eleven years ago, but newer disk and SSD. The only problem with the monitor is that it use much power, so it actually is unpleasant to sit long time before it, especially in summer. I also guess that a larger screen and longer distance to it is better for the eyes, if we have possibility to arrange it at distance.
If i had the budget to upgrade i would buy a TV - less pricey than a monitor, and i do not play game so need not very quick response. Here is one alternative for about 400 EUR: https://www.elgiganten.se/product/ljud- … -43pus6162
Yes i know you are working hard on this on your free time. A big thank you for that
I was thinking to cover more distros with *less* work (except initial learning) for both your protein based and silicon based CPU:s
Of the alternatives, it seem to me Appimage gives the best coverage in return of work, and is easy to use for users
To me it seem easy to package, but this is not "my cup of tea" and i dont know how many obstacles there may be:
"There are different ways to generate an AppImage of your application:
3. Run linuxdeployqt on your Qt application"
"linuxdeployqt takes an application as input and makes it self-contained by copying in the resources that the application uses (like libraries, graphics, and plugins) into a bundle. The resulting bundle can be distributed as an AppDir or as an AppImage"
When used on Qt-based applications, it can bundle a specific minimal subset of Qt required to run the application."
BTW, QET 0.6 final is in Mageia development version "Cauldron" and will be released in current Mageia 6 normal updates but is waiting for a large Qt-Plasma5-etc-depending mess update currently being tested. - Appimage could get past such delays
https://github.com/AppImage/AppImageKit … /README.md
https://github.com/probonopd/linuxdeployqt - also see "known issues"
Did i have money i would donate for your highDPI screen. Once I did (accidentally, in xorg.conf) set up a high X/Y resolution desktop, and panned my physical screen across it (when mouse touched edge). There may be better methods nowadays in your distro of choice. I dont know if that may be an idea to simulate highDPI.
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.
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...
Re: QElectroTech version 0.6 Release Candidate 4 released (2 replies, posted in News)
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
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
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
Re: How Qelectrotech manages old projects (3 replies, posted in EN : Help, suggestions, discussions, ...)
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.