F5, I synced with Github tarball.
Thanks for the tip to tarball.
You are not logged in. Please login or register.
QElectroTech → Posts by scorpio810
F5, I synced with Github tarball.
Thanks for the tip to tarball.
Images is on build folder, yes?
And yes I use git pull and after rsync
I try with Github tarball.
It will push them to switch to the new version. :p
Additionally, i would like to inform that the build files from tuxfamily are actually mixed. You can find some html from QElectroTech 0.8 documentation and some of them from QElectroTech 0.7 documentation
F5 for refresh.
If I change directory to manual_0.8 I need to change URL in QET code, but user use old version don't see new manual.
Great, Thanks Fernando
I synced new changes:
rsync -e ssh -av --delete-after --no-owner --no-g --chmod=g+w --progress /media/backup6/download/qelectrotech-doc/build/ johndoe@ssh.tuxfamily.org:/home/qet/qet-repository/manual_0.7/build/
Merci.
Dans le widget about QET
Bonjour,
si tu pouvais faire l'inventaire des spécifications des machines de celles ou ça fonctionnent bien et celles ou sa fonctionnent beaucoup moins bien.
Sur la 0.8-dev nous avons travaillé à rajouter de nouvelles informations sur les caractéristiques de la machine hôte, ainsi que des logs dans ce but : analyser ce qui perturbe l’expérience utilisateur seulement sur l'OS Windows..
Pour avoir dépanné il y a plus d'une décade de ça un grand nombre de PC Windows de collègues, amis, etc, le problème est souvent lié a un trop grand nombre de programmes inutiles qui tournent en arrière plan, des virus, spywares et autres Malwares, des drivers pas installés ou périmés, Windows ayant aussi la fâcheuse habitude de pourrir seul...
Plugin not work if you don't have conductors connected to terminals.
21:56:36.624 Info: Elements collection reload
21:56:36.630 Info: Elements collection finished to be loaded
With ~ 7000 elements in official collection?
6 ms?
Hello.
The translation is working according to the lazy text from python. On
github you will find the basic chapter in spanish as an example at the
locale/es/LC_MESSAGES folder. You should copy the project source folder and
follow the steps from *sphinx-intl*. The instructions can be found at the
link copied below and the *conf.py* file of the project is already
prepared for that.https://www.sphinx-doc.org/en/master/us … d/intl.htm
To also get the images in the final language, you should create the images
from the folder images/en/ in the desired language, if the images from the
english version are not created they will not be shown in the final
documentation. You will also find some examples in Spanish.At the end of your job, we would appreciate that the final source code from
your folder locale/*xx*/LC_MESSAGES and the image folder are added to the
source repository of the project. These are the folders that the
QElectroTech team has to receive to include in the official github
repository.Best regards
https://forum.kicad.info/t/kicad-fusion … nlab/24891
KiCAD fusion with QElectroTech and MyOpenLab
External Plugins
Sep 22
1 / 9
Sep 22
2d ago

jtm2020hyoHello, I am new in this forum, I write this post with hope than any developer read it.
… actually exist a massiva migration since privative software to open source, in this issue we need be more competitive, for this motive I request a fusion between KiCAD, QElectroTech, and MyOpenLab (Or software similars or equvalents), similar to FreeCAD with KiCAD, this for complement and fight at same level than privative software, integrate all those mentioned software and complement their workflow.
PD: the forum link belongs to a new architect group than are trying to impulse a the open source in new projects, everyone is welcome.
Un élément une fois édité et sauvegardé la miniature change à la volée dans le panel d'élément, il n'est pas utile de recharger la collection, sauf si tu te sers de versions anciennes comme la 0.6, etc.
Je le rajoute. Merci
Salut Seb,
j'ai pas vu passer de PR dernièrement de toi, normal?
Serait tu souffrant? ;-p
Bonsoir,
t'es sur de toi?
Je pense plutôt que les fils ont redessinés leurs chemins et se superposent, suffit de les recadrer. ;-)
These messages are useful during development while compiling, but are not useful to be seen when making packages, they pollute real GCC warnings.
If I dont want to see #pragma messages warnings when I compile for packaging?
QMAKE_CXXFLAGS_WARN_ON += -Wunknown-pragmas
or
QMAKE_CXXFLAGS_WARN_ON += -Wno-unknown-pragmas
not help...
It irritates me to see them, or remove this #prama and keep @TODO?
set # in pro file
DEFINES += QT_DISABLE_DEPRECATED_BEFORE=0x060000
Strange but it compile now on Debian Buster chroot and I don't understand why it's compile without this comment on Ubuntu with Qt 5.9..
Thanks.
Humm, strange build fine on Ubuntu Bionic and focal ..
https://launchpadlibrarian.net/49868991 … ING.txt.gz
QElectroTech → Posts by scorpio810
Powered by PunBB, supported by Informer Technologies, Inc.
Generated in 0.097 seconds (26% PHP - 74% DB) with 6 queries