Il est aussi possible de decouper un gros projets en sous groupes, de la documentation machine, instrument, mais pour cela il faut un ordinateur, tablette.. connectée!!
You are not logged in. Please login or register.
QElectroTech → Posts by scorpio810
Il est aussi possible de decouper un gros projets en sous groupes, de la documentation machine, instrument, mais pour cela il faut un ordinateur, tablette.. connectée!!
Avec ces revois de folios modifiés on peut creer des liens dans un gros projet vers des sous tableaux par exemple?
Il est clair qu'il te faudra les adapter!!
https://download.qelectrotech.org/qet/e … index.html
C'est ce que j'avais utilisé comme workaround en 2015 pour lier mes entées sortie PLC en se basant sur le label du conducteur:
La plus grosse limite n'est pas le nombre de folios, si tu ajoutes trop d'images de tailles importantes, la oui car elles sont encodées en base 64 et décodées lors du lancement du projet.
Apres si tu as aussi des symboles DXF de plusieurs MO chacun il va te falloir une grosse machine ou une grosse workstation pour que le travail reste fluide...
scorpio810 wrote:Ok, merci, mais donc à chaque build, je dois refaire la manip + compiler pour debian (appimage ou deb). C'est pas un problème, ça va juste me faire mettre moins souvent les mises à jours
Mon problème pour windows par contre est que je ne suis pas admin pour installer les outils de compilation. Je vais voir si je peux le faire chez moi dans une VMJe trouve dommage de taper la conf en dur
if (settings.value("diagramcommands/erase-label-on-copy", true).toBool())
alors que permettre à chacun de choisir sa config (par exemple comme about:config de firefox) permet une certaines souplesse.En tout cas merci pour la piste, je regarde ça à la rentrée.
Pas du tout ! L'AppImage utilise le même emplacement pour la config, ouvre le menu aide a propos de QET, va sur l'onglet log: et tu verras les chemins de config, stalesfile, etc, donc suffit de décocher l'option dans la config de QET
23:56:18.975 Info:
23:56:18.975 Info: For QET configuration-files:
23:56:18.975 Info: App Config Location: "/home/laurent/.config/QElectroTech/QElectroTech"
23:56:18.975 Info: For data-files (user-/company-collections, titleblocks, etc.):
23:56:18.975 Info: App Data Location: "/home/laurent/.local/share/QElectroTech/QElectroTech"
23:56:18.975 Info: Directory for project stalefiles:
23:56:18.975 Info: Generic Data Location: "/home/laurent/.local/share/stalefiles/QElectroTech/"
23:56:18.975 Info:
23:56:18.975 Info: Count the elements in your collections (Official-common-collection, company-collections, custom-collections):
23:56:19.051 Info: Elements collection reload
23:56:19.097 Info: Common Elements count: 8574 Elements
23:56:19.111 Info: Custom Elements count: 510 Elements
23:56:19.115 Info: Company Elements count: 205 Elements
23:56:19.115 Info:
23:56:19.115 Info: *** Qt screens ***
23:56:19.115 Info: "( 1 : 3840 x 2160 )"
23:56:19.115 Info: "( 2 : 3840 x 2160 )"
23:56:19.115 Info:
23:56:19.117 Info: DISK : /run
23:56:19.117 Info: FileSystemType: "tmpfs"
23:56:19.117 Info: SizeTotal: 6 GB
23:56:19.117 Info: AvailableSize: 6 GB
23:56:19.117 Info: DISK : /
23:56:19.117 Info: FileSystemType: "ext4"
23:56:19.117 Info: SizeTotal: 79 GB
23:56:19.117 Info: AvailableSize: 19 GB
23:56:19.117 Info: DISK : /run/lock
23:56:19.117 Info: FileSystemType: "tmpfs"
23:56:19.117 Info: SizeTotal: 0 GB
23:56:19.117 Info: AvailableSize: 0 GB
23:56:19.117 Info: DISK : /tmp
23:56:19.117 Info: FileSystemType: "tmpfs"
23:56:19.117 Info: SizeTotal: 33 GB
23:56:19.117 Info: AvailableSize: 33 GB
23:56:19.117 Debug: isReadOnly: true (../sources/machine_info.cpp:238, void MachineInfo::send_info_to_debug())
23:56:19.117 Info: DISK : /run/credentials/systemd-journald.service
23:56:19.118 Info: FileSystemType: "tmpfs"
23:56:19.118 Info: SizeTotal: 0 GB
23:56:19.118 Info: AvailableSize: 0 GB
23:56:19.118 Info: DISK : /home
23:56:19.118 Info: FileSystemType: "ext4"
23:56:19.118 Info: SizeTotal: 902 GB
23:56:19.118 Info: AvailableSize: 389 GB
23:56:19.118 Info: DISK : /media/backup3
23:56:19.118 Info: FileSystemType: "ext4"
23:56:19.118 Info: SizeTotal: 491 GB
23:56:19.118 Info: AvailableSize: 110 GB
23:56:19.118 Info: DISK : /media/backup2
23:56:19.118 Info: FileSystemType: "ext4"
23:56:19.118 Info: SizeTotal: 983 GB
23:56:19.118 Info: AvailableSize: 206 GB
23:56:19.118 Info: DISK : /boot/efi
23:56:19.118 Info: FileSystemType: "vfat"
23:56:19.118 Info: SizeTotal: 0 GB
23:56:19.118 Info: AvailableSize: 0 GB
23:56:19.118 Info: DISK : /media/backup6
23:56:19.118 Info: FileSystemType: "ext4"
23:56:19.118 Info: SizeTotal: 1967 GB
23:56:19.118 Info: AvailableSize: 954 GB
23:56:19.118 Info: DISK : /run/user/1000
23:56:19.118 Info: FileSystemType: "tmpfs"
23:56:19.118 Info: SizeTotal: 6 GB
23:56:19.118 Info: AvailableSize: 6 GB
23:56:19.118 Info: DISK : /run/user/1000/doc
23:56:19.118 Info: FileSystemType: "fuse.portal"
23:56:19.118 Info: SizeTotal: 0 GB
23:56:19.118 Info: AvailableSize: 0 GB
23:56:19.118 Debug: isReadOnly: true (../sources/machine_info.cpp:249, void MachineInfo::send_info_to_debug())
23:56:19.118 Info: DISK USED: /tmp/.mount_QElectggoFOy
23:56:19.119 Info: FileSystemType: "fuse.QElectroTech_0.100.0-r8481-x86_64.AppImage"
23:56:19.119 Info: SizeTotal: 0 GB
23:56:19.119 Info: AvailableSize: 0 GB
23:56:19.119 Info: Count All Elements in collections = 9289 Elements
23:56:19.421 Info: Elements collection finished to be loaded in 0.369 seconds
Tu remarqueras si tu lis le code que tu quand copy/paste un élément tu crées un nouveau UUID et tu effaces les liens.
//this is the first paste, we do some actions for the new element
const QList <Element *> elmts_list = content.m_elements;
for (Element *e : elmts_list)
{
//make new uuid, because old uuid are the uuid of the copied element
e -> newUuid();
if (settings.value("diagramcommands/erase-label-on-copy", true).toBool())
{
//Reset the information about the label, the comment and location
DiagramContext dc = e->elementInformations();
dc.addValue("formula", "");
dc.addValue("label", "");
dc.addValue("comment", "");
dc.addValue("location", "");
e->setElementInformations(dc);
//Reset the text of conductors
const QList <Conductor *> conductors_list = content.m_conductors_to_move;
for (Conductor *c : conductors_list)
{
ConductorProperties cp = c -> properties();
cp.text = c->diagram() ? c -> diagram() -> defaultConductorProperties.text : "_";
c -> setProperties(cp);
}
}
}
}
else
{
const QList<QGraphicsItem *> qgis_list = content.items(filter);
for (QGraphicsItem *item : qgis_list) {
diagram->addItem(item);
}
}
const QList<QGraphicsItem *> qgis_list = content.items();
for (QGraphicsItem *qgi : qgis_list)
qgi -> setSelected(true);
}
The correct approach would be to keep the links to the slaves when you cutting and pasting only a master.
If a master element is deleted, it works well with undo/redo to restore it, so this part of the code should be looked at when someone has time.
Bonsoir peut-être qu'il serait intéressant de le partager ici, non?, afin que d'autres n'est pas a le redessiner;)
Belle journée
Laurent
Bonsoir,
je ne vois pas le problème, avec les éléments de type maitre/esclaves ou avec les éléments xrefs en principe tu devrais t'en sortir?!
Je veux bien que tu nous partagent un exemple de projet basé la dessus. ci besoin en MP!
Ps des projets QET peuvent aller a plusieurs centaines de folios, ok c'est mieux sous Linux que sous Windows....
Je ne sais pas si c'est la cause du pc du taff un dell I5 ...mais j'ai eu de gros crashs, des conducteurs en diagonales .....ce que nous interdisons dans le code .....du rétropédalage de W11 a W10, bref j'ai switché sur le double boot Debian et la no soucis!
Please look video howto section!
This should tell you how QET works, so that the developers don't have to waste time replying to you. Enjoy! ![]()
Bonjour Julien,
tu as essayé avec la dernière 0.100-dev?
https://support.microsoft.com/fr-fr/off … 5339c564c1
Je viens de le tester ça fonctionne sans souci.

Laurent
please see the help menu in the plugin about to use it.
En fait cette option ne sert qu'a définir si on conserve le label, commentaires etc ou non lors de la copie. En aucun cas a re créer de nouveaux liens.
ui->m_save_label_paste->setChecked(settings.value("diagramcommands/erase-label-on-copy", true).toBool());
https://qelectrotech.org/forum/viewtopi … 162#p17162
Bonjour cela ne fonctionne pas pour les renvois de folios, il faut re créer les liens.
Laurent
Hello, this terminal manager has been under development for 3 years, and not finished yet.
But Joshua continues to work on it:
https://github.com/qelectrotech/qelectr … nal_strip/
Please use qet_tb_terminal plugin:
https://qelectrotech.org/forum/viewtopic.php?id=2343
Edit: see this post:
https://qelectrotech.org/forum/viewtopi … 788#p17788
https://qelectrotech.org/forum/viewtopi … 816#p17816
macOS_aarch64 binary
QET_ElementScaler 0.5.4 for macOS intel X86_64
Hallo and thanks Vadoola,
macOS_x86_64 for Intel macOS
My projects are no longer bound but put in a binder in transparencies,
so the diagram pages are better protected from dirt.
Please stop this its the hell when many years after you want to insert new folios:
Bonjour,
je conseille vivement de prendre la 0.100 tu as des versions Apple silicon aarch64 qui sont signés et notariés.
La 0.9 contient des vieux bugs qui ont été depuis longtemps résolus dans la version 0.100.
I build new QET_ElementScaler 0.5.4 macOS aarch64 binary, because binary provided by plc-user didn't work!
Hallo plc-user,
I tried your macOS aarch64 binary on new UTM virtual machine:
https://github.com/plc-user/QET_Element … /tag/0.5.4
The binaries for macos are to be seen as a “trial version” to see if the toolchain from the Docker image works, I don't have the possibility to test the executables.
FYI, QET_ElementScaler was saw as a document, so chmod +x QET_ElementScaler but binary crashed with:
dyld[1287]: Symbol not found: __ZNKSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE4findEPKcm
Referenced from: <D63C1A82-B78B-3F68-82A5-96DD24C5057C> /Users/laurent/Library/Application Support/QElectroTech/QElectroTech/binary/QET_ElementScaler
Expected in: <9FA59D2E-B8CF-39C2-BD5D-C04628AED360> /usr/lib/libstdc++.6.dylibBest regards,
Laurent
macOS arm64 binary
Btw, it's run well only CLI on terminal, on GUI import DXF segfault...
thread 'main' panicked at src/main.rs:65:58:
called `Result::unwrap()` on an `Err` value: Os { code: 30, kind: ReadOnlyFilesystem, message: "Read-only file system" }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Linux Debian unstable binary
See this topic: https://qelectrotech.org/forum/viewtopi … 065#p17065
QET has no network function, so it can't connect to a remote server directly!
The trick is to create a network shared drive on Windows, on linux an maybe macOS create and mount a drive to remote directory.
https://qelectrotech.org/forum/viewtopi … 4173#p4173
Other solution:
https://qelectrotech.org/forum/viewtopic.php?id=2484
At work I use 2 monitors one right for diagram, and I put all widgets like collection, rules numering, selection, etc in left screeen.
I use also QET installed on entreprise remote server for increase power off my PC.
At work my setup is a old I5 intel setup on Debian Linux.
We have installed other Debian in remote server VMware and I use XRDP to run QET on remote server with my 2 monitors on my desktop Debian.
QElectroTech → Posts by scorpio810
Powered by PunBB, supported by Informer Technologies, Inc.
Generated in 0.086 seconds (30% PHP - 70% DB) with 5 queries