Thank you.
About the pgp file, use the one from earlier in this thread:
wget https://download.qelectrotech.org/qet/builds/Flatpak/public.pgp
flatpak lists the version as 0.9-dev, but the abut box in QET say V 0.100.0-dev
You are not logged in. Please login or register.
QElectroTech → Posts by Morganol
Thank you.
About the pgp file, use the one from earlier in this thread:
wget https://download.qelectrotech.org/qet/builds/Flatpak/public.pgp
flatpak lists the version as 0.9-dev, but the abut box in QET say V 0.100.0-dev
Thanks. I put notes in our wiki pointing here.
BTW, I now updated Mageia wiki page https://wiki.mageia.org/en/QElectroTech
I guest is OK to use your logo there.
I know such problems.
We all suffer.
Life, i think it is called.
Varies by time and individual.
Keep up the steam with friends and pleasant activities :-)
Now it works
Brings QElectroTech V 0.100.0-dev
Now if you can fix so main flatpak repo "flathub" provides 0.90 instead of 0.80 that would be great.
Thank you for the continued work
Verified OK in quick test *) on Mageia 8 (64 bit, Plasma):
QElectroTech_0.9-r7759-x86_64.AppImage
QElectroTech_0.100.0-r7832-x86_64.AppImage
From https://download.qelectrotech.org/qet/builds/AppImage/
*) open old schematic and print
Long time no see... passing by to check.
Nice to see there is great activity :-)
And congratulations to the 0.90 release!
Trying per previous post:
wget https://download.qelectrotech.org/qet/builds/Flatpak/public.pgp
404 Not Found
When simply issuing
$ flatpak install Qelectrotech
the "stable" version is found in the flathub repo :-)
But that is version 0.80...
How can we get 0.90 as flatpak? - maybe you should update the flatpak (central)repo as it apparently serve 0.80
And is 0.100 available as flatpak?
Great
Quick test OK on my workstation: Mageia 7 64 bit Plasma, Xorg nvidia-current
Works: New drawing, save, close program, launch again, open, export pdf.
Printing fail: no printer in list to select! (workaround: export pdf)
(FreeCAD installed on same system list printers and can print)
Sidenotes: It would be positive:
§ if the saved file contian program name and ULI to project home page
§ make sure file save name ends in ".qet"
§ make sure saved pdf name ends in ".pdf"
Flatpak user question:
I fail to see how to launch the 0.9 version still installed - listed by "flatpak list", but same Program ID.
Nice to see it is on the way
Flatpak on Ubuntu: https://flatpak.org/setup/Ubuntu/
And then https://qelectrotech.org/forum/viewtopi … 226#p11226
Will give you QET 0.9 dev
For flatpak:
1) Is there a way to specify version? It seems only development version is available?
2) I suppose that like for Appimage, i can add to the launch command the options --common-elements-dir= and --config-dir= ?
I dont have experience from Ubuntu nor snap but a couple workaround suggestions:
(I just tried and QElectroTech_0.8-r7124-x86_64.AppImage do work for me in Mageia 7)
Have you tried other QET versions in Appimage form, i.e 0.9 dev or 0.7 - do they work?
Can you use Ubuntu or Debian packages from https://qelectrotech.org/download.html ?
Do flatpak work for you? (works for me but I dont know if Ubuntu support it)
Next option is to compile it yourself.
That said, yes optimally an Appimage should contain all it need... There was a while the Appimage did not work for me on Mageia, but it got fixed. Also there it complained on GLIBC version https://qelectrotech.org/forum/viewtopi … 8344#p8344
A function to do this would be valuable
Also block duplicate, where connectionsbetween elements in the block are duplicated.
Maybe move could be a subset of same code as duplicate.
That is my highest wish about QET
Hi Rudy
They look really great!
A related side note about drawing complete systems and avoiding neeing to learn and rely on several programs:
QET is perfect for documenting all systems of a machine: electric, pneumatic, fluid, program blocks can all be in same project, and you can link the various parts - so the fluid valve on the pipe drawing is linked to the position sensor in electric schema, and the pneumatic cylinder operating it on the pneumatic schema. The pneumatic valve for the cylinder is linked to its coil on electric schema. The power part of a VFC on a power electrics drawing is linked to its signal part on the control schema. Etc... Symbols are rather easy to create, so i have drawn the specially designed bioreactor vessels like they look like for real, as well as electrical parts, and electronic components to my taste. (Not complete and tidied for sharing, but i draw when i need them)
When the file is closed, use another tool to search and replace?
sed 's|/your/old/part/of/path/|/your/new/part/of/path/|' <old.qet >new.qet
Or is it encoded some way that may wreck that idea?
Nice improvement about wires when a part is removed.
Is there a way to trig that handling automatically - so we can say that all wires of a net is to connect to a by user selected terminal?
That would make it easier to then insert a split or other part in series with another part (where there then is not multiple but only a single wire)
Thank you. Working on Mageia 764bit
(Your appimage dont)
Great, many thanks
Confusing: My system generally have newer versions of the libs, but it is the elder appimages that work here.
Do you have appimage versions between QElectroTech_0.7-r5437-x86_64.AppImage (that works nicely), and current (which does not here), then i can try a few to see where it stopped working.
Yes descriptions are useful i think...
EDIT: versions too, yes
EDIT2: tidying.., practising rpm output formatting...
$ sudo rpm -qa --queryformat '[%-25{NAME} %-7{VERSION} %{SUMMARY}\n]' | grep xcb | sort
lib64qt5xcbqpa5 5.12.6 Qt5 XcbQpa Library
lib64x11-xcb1 1.6.7 X Library
lib64xcb1 1.13.1 X protocol C-language Binding Library
lib64xcb-composite0 1.13.1 X protocol C-language Binding Library (composite extension)
lib64xcb-damage0 1.13.1 X protocol C-language Binding Library (damage extension)
lib64xcb-dpms0 1.13.1 X protocol C-language Binding Library (dpms extension)
lib64xcb-dri2_0 1.13.1 X protocol C-language Binding Library (dri2 extension)
lib64xcb-dri3_0 1.13.1 X protocol C-language Binding Library (dri3 extension)
lib64xcb-glx0 1.13.1 X protocol C-language Binding Library (glx extension)
lib64xcb-icccm4 0.4.1 xcb-icccm library package
lib64xcb-present0 1.13.1 X protocol C-language Binding Library (present extension)
lib64xcb-randr0 1.13.1 X protocol C-language Binding Library (randr extension)
lib64xcb-record0 1.13.1 X protocol C-language Binding Library (record extension)
lib64xcb-render0 1.13.1 X protocol C-language Binding Library (render extension)
lib64xcb-shape0 1.13.1 X protocol C-language Binding Library (shape extension)
lib64xcb-shm0 1.13.1 X protocol C-language Binding Library (shm extension)
lib64xcb-sync1 1.13.1 X protocol C-language Binding Library (sync extension)
lib64xcb-util1 0.4.0 xcb-util library package
lib64xcb-util-cursor0 0.1.3 xcb-util-cursor library package
lib64xcb-util-image0 0.4.0 xcb-util-image library package
lib64xcb-util-keysyms1 0.4.0 xcb-util-keysyms library package
lib64xcb-util-renderutil0 0.3.9 xcb-util-renderutil library package
lib64xcb-xfixes0 1.13.1 X protocol C-language Binding Library (xfixes extension)
lib64xcb-xinerama0 1.13.1 X protocol C-language Binding Library (xinerama extension)
lib64xcb-xinput0 1.13.1 X protocol C-language Binding Library (xinput extension)
lib64xcb-xkb1 1.13.1 X protocol C-language Binding Library (xkb extension)
lib64xcb-xv0 1.13.1 X protocol C-language Binding Library (xv extension)
libx11-xcb1 1.6.7 X Library
libxcb1 1.13.1 X protocol C-language Binding Library
libxcb-dri3_0 1.13.1 X protocol C-language Binding Library (dri3 extension)
libxcb-present0 1.13.1 X protocol C-language Binding Library (present extension)
libxcb-randr0 1.13.1 X protocol C-language Binding Library (randr extension)
libxcb-sync1 1.13.1 X protocol C-language Binding Library (sync extension)
Now i have tried logging out of Plasma, and instead logging into xfce, cinnamon, icewm.
There, I have the exact the same responses from starting the two problematic Appimages.
I have problem decoding French language, but there are tools
I loved designing in QET a couple years ago and hope to utilise it again soon!
I wonder if different package naming mean anything.
On Mageia the 64 systems support both 32 and 64 bit, and the 64 bit libs are named lib64*
Also the paths are /lib/ linked to /usr/lib/ and and /lib64/ linked to /usr/lib64/
Will try in another desktop environment (Mageia support several)
QElectroTech → Posts by Morganol
Powered by PunBB, supported by Informer Technologies, Inc.
Generated in 0.017 seconds (45% PHP - 55% DB) with 5 queries