Search options (Page 15 of 26)

GREAT
it was really a nasty bug!

@ Morganol,

some informations in the wiki are outdated and most of them are only available in french.
At the moment, we're trying to rewrite the website in order to make it really international (all pages in english and french). It will take weeks of work (on free time only...).

I don't care about the wiki at the moment because I think the website is more important to catch new users.

If you want, scorpio810 can give you an account to edit some articles in the wiki (of course, in english).

Super !

T'as utilisé quoi ? Un filtre XSLT ?

Bonjour Opus,

Je crois que tu n'es pas le premier à faire cela
Pour mon travail, je dessine aussi avec QET des plans pneumatiques et hydrauliques directement intégrés dans la documentation électrotechnique de machines CNC.

Non, un conducteur est un conducteur ! QElectroTech ne fait pas la différence entre un conducteur électrique et un tuyau pneumatique ou une conduite hydraulique.
Mais tu peux changer leur apparence en double-cliquant dessus et en allant dans l'onglet "apparence".

Dans la même fenêtre "propriétés des conducteurs", tu peux aussi détourner les champs "fonction" et "tension/protocole" pour entrer des informations que tu pourras utiliser dans les flèches de revoie.
Voir ici pour la mise en place :
https://www.youtube.com/watch?v=xoRwsC17nlo

Pour l'instant, QET n'a pas encore de fonction intégrée qui réalise cela. Et les électriciens en auraient bien besoin aussi !
Malgré tout, nous savons que la faisabilité technique existe déjà car ces informations sont disponibles dans ton projet *.qet sous format xml.
Pour importer ces infos dans un tableur, il faudrait passer par un filtre XSLT qui convertirait le xml écrit par QET en du xml compréhensible par le tableur.
Si tu as envie de t'y mettre, voir ces quelques adresses :
http://www.w3schools.com/xsl/default.asp
http://www.zvon.org/comp/r/tut-XSLT_1.html
https://help.libreoffice.org/Common/Cre … ML_Filters

Les éléments de bonne qualité réalisés avec soin sont toujours les bienvenus

@ Morganol,

at this point, my knowledge is clearly "out of range"
Maybe a developer could say more about those debug infos.

In QET there are now 2 different ways to identify folios:

1. the old way
all folios are identified with continuous numbering (1, 2, 3, 4...).
In this case, folios are numbered with "folio id".
"folio id" is the variable that takes the entries 1, 2, 3, 4...
This variable is AUTOMATICALLY managed and filled by QET. The user can only change the order of the folios but NOT their numbering.

2. the new way
the user would like to number the folio the way he wants.
For example : 10, 20, 30, 40... or A, B, C, D... or Paul, Chantal, Robert, Gertrude... or I, II, III, IV, V...
In this case, the USER has to fill this information in the "folio properties" dialog in the field "folio".
The information "folio number that is typed manually by the user" is named "folio label".

So... if you CHECK the box "Use labels of folio instead of their Id" the table of content of your project (project tree) will look like that:
A - title of the first folio
B - title of the second folio
C - title of the third folio
etc...

or

I - title of the first folio
II - title of the second folio
III - title of the third folio
etc...

if you UNCHECK the box "Use labels of folio instead of their Id" the table of content of your project (project tree) will ALWAYS look like that:
1 - title of the first folio
2 - title of the second folio
3 - title of the third folio
etc...

As I already wrote, these fonctionalities are not totaly achieved (don't forget you're working with the devel version).
They're working but the interactions with the user are not so intuitive.

The default template must be updated.

@ Morganol

not a bug, only something that is not already completely achieved.
To solve the problem:
go to main menu --> Settings --> configure QElectroTech --> New project
then go to the tab "folio" and delete "%id(%total)" in the field "folio :" (under the field "file :") .
But this solve only the problem for new folios you will create.
For existing folios, you have to delete "%id(%total)" in folio properties one by one (or open the *.qet file with a xml editor and use the "search and replace" function).

In the nomenclature (parts list) you can:
EITHER use the column "N° of folio" in the csv file
OR use the column "Label folio" in the csv file

for your information:
"N° of folio" is automaticaly generated by QET if you want CONTINUOUS NUMBERED folios (1, 2, 3...)
"Label folio" receives the entry of the field "folio" of the widget "folio properties" (in this case, you can type by hand the number of the folio or anything you want to identify your folios).

I know... this is a litle bit confusing at the moment but I'm sure it will become easier in the next months (weeks?!?).

@ Opus
this is not a database! Only "something like" a database :-)
The big advantage of possibility 2 is that you have all article data embedded in your symbols.
Drawbacks: you need the LibreOffice macro and it has some restrictions unless you can modify the code of the macro by yourself to shape it fine for your needs.

no problem, I will decide which elements would be good for the QET collection and which not.

mmm... it's the same for me, I only have to know how to read them.

Hi Morganol,

I saw you're creating process symbols for your needs.
If you are ok with it, it would be nice if you send me them so that I can integrate them in the QET collection.
At the moment, there are very few process symbols in the collection.

Of course, you can send me the symbols when you are finished with your job, ther is no hurry!

Send them to:
nuri@qelectrotech.org

Are you creating PID symbols too? For such diagrams:

you have to create it by yourself. The element editor of QET is really easy to use.
When you are finished with it, you can upload your elmt file in the elements repository so that it is integrated in the official QET collection (in a future release).

https://qelectrotech.org/submit-element.php

Hello Robert,

try with the "jump" element.
But be carefull, this element is a bit wrong (it is a very old one and needs some update):
you have to draw some lines under the terminal so that it really looks good on printed document (paper or pdf).
Make some print tests to correct this element!