Or with
/Library/Frameworks/Python.framework/Versions/3.8/bin/qet_tb_generator
You are not logged in. Please login or register.
QElectroTech → Posts by scorpio810
Or with
/Library/Frameworks/Python.framework/Versions/3.8/bin/qet_tb_generator
ok,
now
It 'launch with this command:
python3.8 /Library/Frameworks/Python.framework/Versions/3.8/bin/qet_tb_generator
/Applications/Python\ 3.8/Update\ Shell\ Profile.command ; exit;
Qet_tb_generator path need to be in this path for is open with QET
/Library/Frameworks/Python.framework/Versions/3.8/bin/qet_tb_generator
not in Users/jvdv/Library/Pyhon/3.8 ....
OK, plugin run, but QET search plugin in this path
#elif defined(Q_OS_MAC)
if (openedProjects().count()){
success = process->startDetached("/Library/Frameworks/Python.framework/Versions/3.8/bin/qet_tb_generator", {(QETDiagramEditor::currentProjectView()->project()->filePath())});
}
else {
success = process->startDetached("/Library/Frameworks/Python.framework/Versions/3.8/bin/qet_tb_generator", {("")});
}
When you installed Python3.8 pkg your run Profile.command script?
/Applications/Python\ 3.8/Update\ Shell\ Profile.command ; exit;
Clik on QEt_tb_generator is start?
It 'launch with this command:
python3.8 /Library/Frameworks/Python.framework/Versions/3.8/bin/qet_tb_generator
Hi and thanks for compliments,
what your OS?
QET version?
How you install qet_tb_generator?
Ok, fixed.
Testerai ce soir en rentrant du boulot.
Il n'y a pas eut de changement sur ce code récemment, et les builds précédents sont passés..
Hmm, not fixed, strange FTBFS on Debian Buster:
sources/editor/ui/elementpropertieseditorwidget.cpp: In member function 'void ElementPropertiesEditorWidget::on_m_base_type_cb_currentIndexChanged(int)':
sources/editor/ui/elementpropertieseditorwidget.cpp:259:17: error: 'class QTabWidget' has no member named 'setTabVisible'; did you mean 'setVisible'?
ui->tabWidget->setTabVisible(1,
^~~~~~~~~~~~~
setVisible
g++ -c -pipe -std=c++17 -g -O2 -fdebug-prefix-map=/build/qelectrotech-0.90.r7168=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu++11 -Wall -W -D_REENTRANT -fPIC -DQET_ALLOW_OVERRIDE_CED_OPTION -DQET_ALLOW_OVERRIDE_CTBTD_OPTION -DQET_ALLOW_OVERRIDE_CD_OPTION -DQET_EXPORT_PROJECT_DB -DQAPPLICATION_CLASS=QApplication -DQT_MESSAGELOGCONTEXT -DQET_LANG_PATH=/usr/share/qelectrotech/lang/ -DQET_COMMON_COLLECTION_PATH=/usr/share/qelectrotech/elements/ -DQET_COMMON_TBT_PATH=/usr/share/qelectrotech/titleblocks/ -DQT_NO_DEBUG -DQT_SVG_LIB -DQT_PRINTSUPPORT_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_XML_LIB -DQT_SQL_LIB -DQT_CONCURRENT_LIB -DQT_CORE_LIB -I. -ISingleApplication -Isources/ui -isystem /usr/include/i386-linux-gnu/qt5 -isystem /usr/include/i386-linux-gnu/qt5/QtSvg -isystem /usr/include/i386-linux-gnu/qt5/QtPrintSupport -isystem /usr/include/KF5/KWidgetsAddons -isystem /usr/include/i386-linux-gnu/qt5/QtWidgets -isystem /usr/include/i386-linux-gnu/qt5/QtGui -isystem /usr/include/i386-linux-gnu/qt5/QtNetwork -isystem /usr/include/i386-linux-gnu/qt5/QtXml -isystem /usr/include/i386-linux-gnu/qt5/QtSql -isystem /usr/include/i386-linux-gnu/qt5/QtConcurrent -isystem /usr/include/KF5/KCoreAddons -isystem /usr/include/i386-linux-gnu/qt5/QtCore -Irelease -isystem /usr/include/libdrm -I. -I/usr/lib/i386-linux-gnu/qt5/mkspecs/linux-g++ -o release/partline.o sources/editor/graphicspart/partline.cpp
g++ -c -pipe -std=c++17 -g -O2 -fdebug-prefix-map=/build/qelectrotech-0.90.r7168=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu++11 -Wall -W -D_REENTRANT -fPIC -DQET_ALLOW_OVERRIDE_CED_OPTION -DQET_ALLOW_OVERRIDE_CTBTD_OPTION -DQET_ALLOW_OVERRIDE_CD_OPTION -DQET_EXPORT_PROJECT_DB -DQAPPLICATION_CLASS=QApplication -DQT_MESSAGELOGCONTEXT -DQET_LANG_PATH=/usr/share/qelectrotech/lang/ -DQET_COMMON_COLLECTION_PATH=/usr/share/qelectrotech/elements/ -DQET_COMMON_TBT_PATH=/usr/share/qelectrotech/titleblocks/ -DQT_NO_DEBUG -DQT_SVG_LIB -DQT_PRINTSUPPORT_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_XML_LIB -DQT_SQL_LIB -DQT_CONCURRENT_LIB -DQT_CORE_LIB -I. -ISingleApplication -Isources/ui -isystem /usr/include/i386-linux-gnu/qt5 -isystem /usr/include/i386-linux-gnu/qt5/QtSvg -isystem /usr/include/i386-linux-gnu/qt5/QtPrintSupport -isystem /usr/include/KF5/KWidgetsAddons -isystem /usr/include/i386-linux-gnu/qt5/QtWidgets -isystem /usr/include/i386-linux-gnu/qt5/QtGui -isystem /usr/include/i386-linux-gnu/qt5/QtNetwork -isystem /usr/include/i386-linux-gnu/qt5/QtXml -isystem /usr/include/i386-linux-gnu/qt5/QtSql -isystem /usr/include/i386-linux-gnu/qt5/QtConcurrent -isystem /usr/include/KF5/KCoreAddons -isystem /usr/include/i386-linux-gnu/qt5/QtCore -Irelease -isystem /usr/include/libdrm -I. -I/usr/lib/i386-linux-gnu/qt5/mkspecs/linux-g++ -o release/partpolygon.o sources/editor/graphicspart/partpolygon.cpp
g++ -c -pipe -std=c++17 -g -O2 -fdebug-prefix-map=/build/qelectrotech-0.90.r7168=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu++11 -Wall -W -D_REENTRANT -fPIC -DQET_ALLOW_OVERRIDE_CED_OPTION -DQET_ALLOW_OVERRIDE_CTBTD_OPTION -DQET_ALLOW_OVERRIDE_CD_OPTION -DQET_EXPORT_PROJECT_DB -DQAPPLICATION_CLASS=QApplication -DQT_MESSAGELOGCONTEXT -DQET_LANG_PATH=/usr/share/qelectrotech/lang/ -DQET_COMMON_COLLECTION_PATH=/usr/share/qelectrotech/elements/ -DQET_COMMON_TBT_PATH=/usr/share/qelectrotech/titleblocks/ -DQT_NO_DEBUG -DQT_SVG_LIB -DQT_PRINTSUPPORT_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_XML_LIB -DQT_SQL_LIB -DQT_CONCURRENT_LIB -DQT_CORE_LIB -I. -ISingleApplication -Isources/ui -isystem /usr/include/i386-linux-gnu/qt5 -isystem /usr/include/i386-linux-gnu/qt5/QtSvg -isystem /usr/include/i386-linux-gnu/qt5/QtPrintSupport -isystem /usr/include/KF5/KWidgetsAddons -isystem /usr/include/i386-linux-gnu/qt5/QtWidgets -isystem /usr/include/i386-linux-gnu/qt5/QtGui -isystem /usr/include/i386-linux-gnu/qt5/QtNetwork -isystem /usr/include/i386-linux-gnu/qt5/QtXml -isystem /usr/include/i386-linux-gnu/qt5/QtSql -isystem /usr/include/i386-linux-gnu/qt5/QtConcurrent -isystem /usr/include/KF5/KCoreAddons -isystem /usr/include/i386-linux-gnu/qt5/QtCore -Irelease -isystem /usr/include/libdrm -I. -I/usr/lib/i386-linux-gnu/qt5/mkspecs/linux-g++ -o release/partrectangle.o sources/editor/graphicspart/partrectangle.cpp
g++ -c -pipe -std=c++17 -g -O2 -fdebug-prefix-map=/build/qelectrotech-0.90.r7168=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu++11 -Wall -W -D_REENTRANT -fPIC -DQET_ALLOW_OVERRIDE_CED_OPTION -DQET_ALLOW_OVERRIDE_CTBTD_OPTION -DQET_ALLOW_OVERRIDE_CD_OPTION -DQET_EXPORT_PROJECT_DB -DQAPPLICATION_CLASS=QApplication -DQT_MESSAGELOGCONTEXT -DQET_LANG_PATH=/usr/share/qelectrotech/lang/ -DQET_COMMON_COLLECTION_PATH=/usr/share/qelectrotech/elements/ -DQET_COMMON_TBT_PATH=/usr/share/qelectrotech/titleblocks/ -DQT_NO_DEBUG -DQT_SVG_LIB -DQT_PRINTSUPPORT_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_XML_LIB -DQT_SQL_LIB -DQT_CONCURRENT_LIB -DQT_CORE_LIB -I. -ISingleApplication -Isources/ui -isystem /usr/include/i386-linux-gnu/qt5 -isystem /usr/include/i386-linux-gnu/qt5/QtSvg -isystem /usr/include/i386-linux-gnu/qt5/QtPrintSupport -isystem /usr/include/KF5/KWidgetsAddons -isystem /usr/include/i386-linux-gnu/qt5/QtWidgets -isystem /usr/include/i386-linux-gnu/qt5/QtGui -isystem /usr/include/i386-linux-gnu/qt5/QtNetwork -isystem /usr/include/i386-linux-gnu/qt5/QtXml -isystem /usr/include/i386-linux-gnu/qt5/QtSql -isystem /usr/include/i386-linux-gnu/qt5/QtConcurrent -isystem /usr/include/KF5/KCoreAddons -isystem /usr/include/i386-linux-gnu/qt5/QtCore -Irelease -isystem /usr/include/libdrm -I. -I/usr/lib/i386-linux-gnu/qt5/mkspecs/linux-g++ -o release/partterminal.o sources/editor/graphicspart/partterminal.cpp
make[2]: *** [Makefile.Release:7318: release/elementpropertieseditorwidget.o] Error 1
make[2]: *** Waiting for unfinished jobs....
Added, thanks Thomas for his PR.
https://www.kdab.com/kdsingleapplication/
What is a single-instance policy?
Single-instance policy refers to those applications that want to spawn a unique instance for a given user session. Even when launched multiple times, such applications will not spawn a number of separate instances. Instead, the existing instance will be notified, somehow, and some action will be taken by that instance. Typically, its window will be shown (if hidden) and raised to the foreground.This mechanism works even when the application is launched indirectly, like from a file manager when opening a file type associated with the application. In this case, the new instance (launched by the file manager) will simply tell the existing instance to open the selected file, and then the new instance will immediately quit.
The problem is: on most operating systems we do normally get a new instance every time we launch an application! Therefore, some logic is needed to honor a single-instance policy. KDSingleApplication implements such logic.
@ Achim: good catch. ;-)
BTW, if you have some spare time to translate QET interface to Lithuanian, you 're welcome.
Is easy and if you know GIt is better.
Why keep QET open, is very slow to launch on your OS?
For very large projects, every day I increment the name of the project with a new date, I save it locally and I also share it on one of the NAS (Network Attached Storage) of the service.
Hi,
FYI, I tried to add qet-tb-generator addon in org.qelectrotech.QElectroTech flatpak package
https://download.qelectrotech.org/qet/s … oTech.jsonhttps://github.com/qelectrotech/qelectr … 4e97bcacf6
, but tkinter Python module isn't provided yet with flatpak upstream :Launching qet-tb-generator under Qet flatpak :
flatpak run --command=qelectrotech org.qelectrotech.QElectroTech Qt: Session management error: Could not open network socket org.kde.knotifications: env says KDE is running but SNI unavailable -- check KDE_FULL_SESSION and XDG_CURRENT_DESKTOP QETProject::toXml() : exporting diagram "References Page" [ Diagram(0x5643bcd2cea0) ] QETProject::toXml() : exporting diagram "Mains Power Supply" [ Diagram(0x5643c0ebeaa0) ] QETProject::toXml() : exporting diagram "Auxiliary Power Supply" [ Diagram(0x5643c0ec3220) ] QETProject::toXml() : exporting diagram "Emergency Stop Circuit" [ Diagram(0x5643c0eaaa80) ] QETProject::toXml() : exporting diagram "Emergency Stop Power" [ Diagram(0x5643c1183580) ] QETProject::toXml() : exporting diagram "VX Gate Control Circuit" [ Diagram(0x5643c12f5740) ] QETProject::toXml() : exporting diagram "V1 Gate Control Circuit" [ Diagram(0x5643c1358c50) ] QETProject::toXml() : exporting diagram "V2 Gate Control Circuit" [ Diagram(0x5643c1592f50) ] QETProject::toXml() : exporting diagram "V3 Gate Control Circuit" [ Diagram(0x5643c17490d0) ] QETProject::toXml() : exporting diagram "V4 Gate Control Circuit" [ Diagram(0x5643c15960f0) ] QETProject::toXml() : exporting diagram "V5 Gate Control Circuit" [ Diagram(0x5643c0ed33a0) ] QETProject::toXml() : exporting diagram "V6 Gate Control Circuit" [ Diagram(0x5643c1e6fef0) ] QETProject::toXml() : exporting diagram "V7 Gate Control Circuit" [ Diagram(0x5643c1f323c0) ] QETProject::toXml() : exporting diagram "A0 PLC Layout" [ Diagram(0x5643c2116a40) ] QETProject::toXml() : exporting diagram "A0 Input Module" [ Diagram(0x5643c229ece0) ] QETProject::toXml() : exporting diagram "A0 Output Module" [ Diagram(0x5643c2260010) ] QETProject::toXml() : exporting diagram "A1/1 Input Module" [ Diagram(0x5643c230eff0) ] QETProject::toXml() : exporting diagram "A1/2 Input Module" [ Diagram(0x5643c23fff70) ] QETProject::toXml() : exporting diagram "A1 Output Module" [ Diagram(0x5643c263b210) ] QETProject::toXml() : exporting diagram "A2/1 Input Module" [ Diagram(0x5643c2746770) ] QETProject::toXml() : exporting diagram "A2/2 Input Module" [ Diagram(0x5643c27f2790) ] QETProject::toXml() : exporting diagram "A2 Output Module" [ Diagram(0x5643c28a3550) ] QETProject::toXml() : exporting diagram "A3/1 Input Module" [ Diagram(0x5643c29a0190) ] QETProject::toXml() : exporting diagram "A3/2 Input Module" [ Diagram(0x5643c2a4c670) ] QETProject::toXml() : exporting diagram "A3 Output Module" [ Diagram(0x5643c2afcfd0) ] QETProject::toXml() : exporting diagram "A4/1 Input Module" [ Diagram(0x5643c2b8ff40) ] QETProject::toXml() : exporting diagram "A4/2 Input Module" [ Diagram(0x5643c2ca5940) ] QETProject::toXml() : exporting diagram "A4 Output Module" [ Diagram(0x5643c2cc4740) ] QETProject::toXml() : exporting diagram "A5/1 Ana Input Module" [ Diagram(0x5643c2d248b0) ] QETProject::toXml() : exporting diagram "A5/2 Ana Input Module" [ Diagram(0x5643c2dfdb10) ] QETProject::toXml() : exporting diagram "TB1 Terminal Bord" [ Diagram(0x5643c2e7bf80) ] QETProject::toXml() : exporting diagram "TB2 Terminal Bord" [ Diagram(0x5643c300a030) ] QETProject::toXml() : exporting diagram "TB3 Terminal Bord" [ Diagram(0x5643c3146e80) ] QETProject::toXml() : exporting diagram "TB4 Terminal Bord" [ Diagram(0x5643c31cf060) ] QETProject::toXml() : exporting diagram "TB5 Terminal Bord" [ Diagram(0x5643c3089dc0) ] QETProject::toXml() : exporting diagram "PB1 Panel Front View" [ Diagram(0x5643c32ed320) ] QETProject::toXml() : exporting diagram "PB2 Panel Front View" [ Diagram(0x5643c33001a0) ] QETProject::toXml() : exporting diagram "CX1 Modbus TCP" [ Diagram(0x5643c3453470) ] Traceback (most recent call last): File "/app/bin/qet_tb_generator", line 11, in <module> load_entry_point('qet-tb-generator==1.1.5', 'console_scripts', 'qet_tb_generator')() File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 489, in load_entry_point return get_distribution(dist).load_entry_point(group, name) File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 2852, in load_entry_point return ep.load() File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 2443, in load return self.resolve() File "/usr/lib/python3.7/site-packages/pkg_resources/__init__.py", line 2449, in resolve module = __import__(self.module_name, fromlist=['__name__'], level=0) File "/app/lib/python3.7/site-packages/src/main.py", line 113, in <module> import tkinter as tk ModuleNotFoundError: No module named 'tkinter'
https://gitlab.com/freedesktop-sdk/free … uests/4569
Nice ;-)
I will try to work on it again and test when I have free time ...
Update "org.kde.Platform",
to "runtime-version": "5.15", packages is available.
submit Flatpak to Flathub
https://github.com/qelectrotech/qelectr … issues/143
https://github.com/flathub/flathub/pull/2146
Fatal: ASSERT failure in QList<T>::at: "index out of range", file /usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h, line 571 (/usr/include/x86_64-linux-gnu/qt5/QtCore/qlist.h:571, )
Hmm qlist.h
inline void QList<T>::removeAt(int i)
{
#if !QT_DEPRECATED_SINCE(5, 15)
Q_ASSERT_X(i >= 0 && i < p.size(), "QList<T>::removeAt", "index out of range");
#endif
if (i < 0 || i >= p.size()) {
#if !defined(QT_NO_DEBUG)
qWarning("QList::removeAt(): Index out of range.");
#endif
return;
#if QT_DEPRECATED_SINCE(5, 14) && QT_VERSION < QT_VERSION_CHECK(6,0,0)
QT_DEPRECATED_VERSION_X_5_14("Use QList<T>(set.begin(), set.end()) instead.")
static QList<T> fromSet(const QSet<T> &set);
QT_DEPRECATED_VERSION_X_5_14("Use QSet<T>(list.begin(), list.end()) instead.")
QSet<T> toSet() const;
QT_DEPRECATED_VERSION_X_5_14("Use QList<T>(list.begin(), list.end()) instead.")
static inline QList<T> fromStdList(const std::list<T> &list)
{ return QList<T>(list.begin(), list.end()); }
QT_DEPRECATED_VERSION_X_5_14("Use std::list<T>(list.begin(), list.end()) instead.")
inline std::list<T> toStdList() const
{ return std::list<T>(begin(), end()); }
#endif
Hi,
you could share your project?
Apres quelques galères avec certains changements d'outil de packaging Debian : devscripts, dh-autoreconf, pbuilder etc .. les paquets sont de nouveau disponibles sur le PPA :
Upgrade du pinning :
sudo sed -i 's/'"version 0.80.*"'/'"version 0.90.*"'/' /etc/apt/preferences.d/40qelectrotech-devel
Added Groovy packages for next builds on PPA
Je n'ai pas encore pris le temps d'essayer, mais si plusieurs personnes confirment que le chargement est plus raide on ajoutera ce commit à la 0.8.1.
Le chargement plus raide ... heu si tu veux
Quelques cherry-pic et c'est déja ajouté sur la branche 0.8.1.
Maintenant j'attend les remarques et surtout les logs de nos 2 râleurs de service, ils se reconnaîtrons ..
D’après mes tests la maj de pugiXML n'a pas amélioré le temps de chargement, celle de SingleApplication : à par contre divisé sur les deux machines de tests le temps de lancement par dix.
premier pc de test: laptop hp elitebook 850 g5 i7 UHD + 16 G RAM + SSD MVME M.2 - PCI-E 3.0 4x
second pc de test: Ryzen 1600X 16 G RAM MSI b350 tomahawk+ SSD sata
QElectroTech → Posts by scorpio810
Powered by PunBB, supported by Informer Technologies, Inc.
Generated in 0.105 seconds (27% PHP - 73% DB) with 6 queries