@Re-searcher about this element you must not take to account the 'bug', see my previous post (element was made with qet 0.7 dev).
For this element, what we need is to edit it in element editor, save it and everything will be ok.
If you encounter the same bug for another element let me know.
151 2022-02-03 15:12:01
Re: Messed up / scrambled elements (14 replies, posted in EN : Help, suggestions, discussions, ...)
152 2022-02-02 11:57:37
Re: Messed up / scrambled elements (14 replies, posted in EN : Help, suggestions, discussions, ...)
If someone have the skill and time to write a software to update the .elmt file version. It will be great, especially for qet 2.0.
153 2022-02-02 11:54:35
Re: Messed up / scrambled elements (14 replies, posted in EN : Help, suggestions, discussions, ...)
Ok I understand what going on,
the element was created with 0.7 devel BUT during development of qet 0.7 the way how font (of dynamic text item) was saved was changed. Your element was created before the change.
Now it work in diagram editor because there is a retrocompatibility code, but not in element editor because in element editor it's easy to rework the element and save it (which will be up to date with how font are saved in element file).
Don't forget when you use a development version everything you do can be break from one day to another. We are very happy when you (users) play with the development version and tell us what it good or not, what is bugged, what can be improved etc.... I do my best to give you development version with less bug as possible, but it's remains development version.
Laurent, I don't understand why you got the problem on both editor. Screen size ?
154 2022-02-02 11:24:28
Re: Messed up / scrambled elements (14 replies, posted in EN : Help, suggestions, discussions, ...)
Ok I also got the problem,
element is ok on diagram editor but not in element editor.
Hello Re-searcher,
Strange what you say, I do test :
Create one element by version 0.6 0.7 0.8 0.9 (4 elements) and I open each elements with each versions and except when I try to open element created with version 0.7 or higher in qet 0.6 (which in normal because dynamic text was created in version 0.7) everything work well, and I don't see difference in the font attribute on the xml file.
Have you got an exemple please.
155 2022-01-26 23:41:47
Re: Texts are displayed different size on different computers (36 replies, posted in EN : Help, suggestions, discussions, ...)
Hello, it's normal you can't see a difference because the test is wrong.
To test, you need to do these few steps :
-Install the qelectrotech pixel_size_font build on both computers (HD laptop and 4K laptop) and only use this qelectrotech version for the test.
-Create a new project in computer 1, save it and open it in computer 2.
-See the difference
-Create a new project in computer 2, save it and open it in computer 1.
-See the difference.
-Tell us if they work or not.
The test must be done ONLY in this way. If the text size is good, we can go further.
Best regard
Joshua.
156 2022-01-15 00:44:59
Re: actual Version does not find common element-collection (4 replies, posted in EN : Help, suggestions, discussions, ...)
Fixed
157 2022-01-13 20:25:25
Re: Position du texte pour les éléments liés (ex:3/3-C4) et rep de contact (5 replies, posted in FR : Aide, suggestions, discussions, ...)
Salut,
alors c'est vrai que tout ça est un peu complexe quand on découvre qet car c'est effectivement pas toujours claire (à cause de l'historique et de la dette technique de qet).
Quoi qu'il en soit :
%f ne donne pas le numéro de folio mais sa position (nuance)
%F donne le nom du folio. Ce nom tu le retrouve dans les propriété du folio dans le champ Folio, et celui-ci peut comporter des variables dont entre autres la position du folio et la quantité de folio.
Pour l'histoire des Xref des esclaves, gauche/droite/dessus/dessous c'est par rapport au texte sur lequel il est 'agrippé' et alignement du texte signifie que la Xref sera positionné comme la propriété "alignement" du texte en question.
158 2022-01-10 20:09:58
Re: Affichage d'une règle pour cotation ou dimension (16 replies, posted in FR : Aide, suggestions, discussions, ...)
No of course we don’t want to exclude anonyone
.
It’s true it’s very more easy for us to speak french.
About the thumbnail scale, I think we can create a new thread in english and this thread will be the continuity of this one : https://qelectrotech.org/forum/viewtopi … 247#p14247
Why a new thread ? Because the first post will be a resume of all ideas submitted in this thread and everyone can see the evolution in the first post instead of read all the thread.
About size I think 1px = 1mm is enough the goal of Qet is not to draw in very realistic way an electrical cabinet, but it's true that font become too small with this scale.
One thing is sure, the scale must be a multiple of 1 (1:1, 1:2) but not something like 1:2.2
At the end, no matter what scale we choose, for me it's the same to code.
Some things I can quickly add (when a scale will chosen) is a little ruler tool in the element editor, to help the drawing.
One other thing is to create a new category in the element collection for the new elements with the good size, then we are sure all element inside have the same scale.
In my opinion, a fine level of detail is not necessary for large control cabinets. So only "rough" rectangles for the devices would be necessary for this scope of application. Then we wouldn't even need the detailed images we already have in the common collection. Do you want to achieve that? I hope: no!
Not sure to understand well the "I hope: no!" . You want or not want "rough" rectangles for large cabinet ?
My opinion, we can have both and I already though about that.
We need to add new information about the element (width, height, depth), then with these information Qet can automatically add lambda rectangle for every device, and user only need to arrange the disposition of these rectangle.
But this feature need lot of work, and first, it's not the actual priority feature, second this feature need some deep change and will probably be a better place in Qet 2.0 (in 2100
) https://qelectrotech.org/wiki_new/refon … lectrotech sorry it's in french but this wiki page is more a memory help /todo list for me than a road map .
Before we (you, Joshua!) implement anything in the source code, we should agree on where the journey with QET should go!
Depending on which areas we want to cover with QET, we may annoy other users. Therefore we should think carefully about what we decide.
I could just repeat the arguments and suggestions from my posts in the other threads mentioned here. But please read for yourself ...
The journey of Qet is very clear, be an industrial electrical designing software, like eplan or see electrical for the most well know, of course Qet will never be as complete as these software, I haven't got the skills and the time for that.
159 2022-01-07 20:00:36
Re: Affichage d'une règle pour cotation ou dimension (16 replies, posted in FR : Aide, suggestions, discussions, ...)
Oui de l'éditeur d'élément.
Pour le nom de la section peut importe, du moment que c'est clair pour tout le monde.
D'ailleurs pendant qu'on y est, je vais ajouter un nouveau type d'élément "vignette" ça sera utile par la suite de différencier les éléments schématique et leurs représentations de mise en armoire
160 2022-01-07 18:26:20
Re: Affichage d'une règle pour cotation ou dimension (16 replies, posted in FR : Aide, suggestions, discussions, ...)
Je pense partir sur 1px = 1mm, ça permet de faire des dessins assez précis (en tout cas suffisamment pour des mises en armoire).
Beaucoup d'élément actuel ne sont pas à la bonne cote mais de toute façon peut importe l’échelle choisis il y aurait forcément eu des éléments à reprendre.
Pour les dimensions (ta capture d’écran) c’est à titre informatif il ne faut pas se baser dessus (pour diverse raison).
Au sujet des bornes et du texte c’est obligé d’être pris en compte pour des raisons techniques, par contre il faut bien faire la différence entre les deux type de texte : les textes éditables ne sont pas pris en compte, seuls les textes fixe le sont.
Dans les spinbox (les boutons permettant de régler les dimensions des parties graphiques) il n’y a aucune indication d’unité (ce sont des pixels en fait) je vais mettre ‘mm’ après la valeur, ce sera clair comme ça.
Je pense mettre en place rapidement un petit outil de cotation dans l’éditeur d’élément, MAIS ATTENTION se sera juste un outil d’aide pour la création d’élément, celui-ci n’apparaîtra pas sur l’éditeur de schéma et ne sera pas non plus sauvegardé, c’est-à-dire qu’une fois l’éditeur fermé si vous rouvrez à nouveau le même élément tous les outils de cotation auront disparu.
Faut-il créer une nouvelle section dans la collection d’élément avec les vignettes de mise en armoire à la bonne cote (à coter de celle existante), afin d’avoir une section dans lequel on est sûre que tous les éléments sont à la même échelle, l’ancienne section pourra être purgée au fur et à mesure ?
Moi je vote oui.
161 2022-01-05 20:51:38
Re: Affichage d'une règle pour cotation ou dimension (16 replies, posted in FR : Aide, suggestions, discussions, ...)
En fait dans QElectroTech il n’y a jamais eu de cotation.
Faute de cotation chacun y est allé de son ressentit personnel (X px = 1mm) pour créer les éléments dont il avait besoins.
Ensuite étant donné que l’écrasante majorité des éléments provient des utilisateurs qui nous envoient leur propre éléments, nous les avons intégrées tel quel afin que tous le monde puisse en profiter même si dans le cas présent l’échelle n’est pas identique.
Idéalement il faudrait imposer une règle (X px = 1mm) pour tout le monde, ou encore mieux avoir un vrai outil de cotation (mais encore une fois toujours le même problème de temps).
Il est aussi possible que quelqu’un de très très motivé redessine tous les éléments avec la même échelle, mais ça représente une tâche énorme (tu t’en es rendu compte avec tes deux disjoncteurs).
162 2022-01-02 14:14:03
Re: Texts are displayed different size on different computers (36 replies, posted in EN : Help, suggestions, discussions, ...)
About this commit :
Only the editable texts of elements are changed.
To test it, open the project who have font size problem on the good screen, save it in an other name, re-open the new file and test it.
If everything work well we can add these changes to other texts of qet.
163 2021-12-28 21:10:09
Re: Texts are displayed different size on different computers (36 replies, posted in EN : Help, suggestions, discussions, ...)
After a few test, I think the problem come from the difference between a font size set by point or pixel (there is a lot of information on internet about this) but in a few words:
point size -> font size look same for human no matter if screen a low resolution or a 1000K resolution.
Pixel size -> the font use always the same pixel width and height no matter the screen resolution : example if screen is low resolution and font look good the same font on 4k will look very very small.
In qet we use pointSize and I think the problem come from that. Use pixelSize for diagram font is not difficult but there is some other part of qet that will be cause issue
.
For the texts of elements I think I can fix it without a lot of effort, but for the independent text item this is an other pair of sleeves...
The text are automatically saved in html in the .qet file even if you don't use html formating. The html only write the pointSize of font and not the pixelSize, not impossible to do this, but probably not easy.
For fix it I need to :
-use pixelSize instead of pointSize.
-Independent text by default be a simple text and not formatted to html and when are saved, save it as simple text or html formatted according to what he was.
With these two points I think I can fix the problem of font size between hd and 4k screen.
164 2021-12-28 19:38:56
Re: Texts are displayed different size on different computers (36 replies, posted in EN : Help, suggestions, discussions, ...)
Hello ruggedvid.
I try with my win10 work laptop and I've got the bug.
At this time I haven't got any solution, but I probably have enough stuff to find it.
I will work on it and twist my fingers for a solution that work with existing files and not only with news.
165 2021-12-26 16:37:14
Re: actual Version does not find common element-collection (4 replies, posted in EN : Help, suggestions, discussions, ...)
Probably a wrong path is returned by the function.
But when I will fix this problem, the performance improvement will stay
.
Happy to see that now, even if qet stay speeder in linux than windows, the performance on this last one is now closer to linux.
166 2021-12-24 14:16:09
Re: actual Version does not find common element-collection (4 replies, posted in EN : Help, suggestions, discussions, ...)
Yes one of my colleague report me this issue.
I think they come from this commit : https://git.tuxfamily.org/qet/qet.git/c … f509e23332
I will take a look this week.
167 2021-12-22 20:11:49
Re: Différence taille police entre MAC et PC (9 replies, posted in FR : Aide, suggestions, discussions, ...)
Dans les propriétés de QElectroTech essai de modifier la méthode de mise à l’échelle.
Les problèmes de textes sont sur tous les textes (textes éditable et textes fixe) ou que les textes éditable ?
168 2021-12-22 19:26:30
Re: Texts are displayed different size on different computers (36 replies, posted in EN : Help, suggestions, discussions, ...)
By default qet use sans serif font.
If you change font make sure, the font is also present in other computer.
But I don't think your problem come from font family.
169 2021-12-22 19:16:39
Re: Différence taille police entre MAC et PC (9 replies, posted in FR : Aide, suggestions, discussions, ...)
Qu'elle sont les définitions des écrans ?
170 2021-12-14 22:31:35
Re: Texts are displayed different size on different computers (36 replies, posted in EN : Help, suggestions, discussions, ...)
It's very hard without 4k screen to test it.
Can you send us your project, and also the last log of qet (you can found the log in the about qet dialog).
The wrong scale appear on all element text, editable and not editable text or only on editable text ?
171 2021-12-08 20:06:01
Re: elements connectors slip apart (36 replies, posted in Elements)
Hello mezga, first of all qet 0.7 is an old version, please install the 0.8 version and test again.
About your problem, may be it's just the titleblock editor is opened behind the diagram editor of QElectrotech.
For the video, you can't add it directly in the forum. You need for exempleto upload it in youtube and paste the link in the forum.
Joshua
172 2021-12-02 19:03:39
Re: Voltage/Protocol missing in element information (4 replies, posted in EN : Help, suggestions, discussions, ...)
This feature (comment in a frame snapped below the Xref) was removed since a while.
Instead you need to add an element text, and set it to display comment.
173 2021-11-28 12:25:19
Topic: Logiciel d'enregistrement/restauration de tag basé sur pylogix (0 replies, posted in Bar Fourre-tout)
Dans le cadre de mon boulot j'ai développé un petit bout de logiciel (un script évoluer je devrais dire) qui utilise pylogix. https://github.com/dmroeder/pylogix
Rien de bien sensationnel, il permet de se connecter et vérifier que la com est bien établie avec l'automate et (le but du logiciel) récupérer les tags de l'automate puis les écrire dans un fichier sur le pc et faire la manip inverse (on peut écrire dans autant de fichier différent que l'on veut).
Le logiciel ne découvre pas tout seul les tags de l'automate il faut lui renseigner les tags qu'il doit lire/écrire dans un fichier précis.
Le soft est assez spécifique par rapport aux besoins initiaux, mais je pense que celui-ci sera un peu amélioré afin d’être un poil plus générique (demande d’un collègue).
Est ce que cela intéresse quelqu’un d'avoir les sources ? Bon au préalable il faut que je demande à mon chef si je peux mettre les sources en libre mais je ne pense pas qu'il sera contre.
174 2021-11-28 12:09:38
Re: It takes too long time to open a file *.qet (26 replies, posted in EN : Help, suggestions, discussions, ...)
Hello Mike,
Actually the terminal manager is in development and should not be used for real project, prefer use unalcalde's QET TB Generator witch work very well.
Of course you can test the terminal manager and report bugs, ideas/something you want to have for this functionality, in this topic https://qelectrotech.org/forum/viewtopic.php?id=1957 the topic is in french but you can write a post in English.
PS : I take a look at your website, I'm very impressed a company like your (High precision valve test) use our modest software.
I'm always (probably Laurent and all contribs of QET) very interested and content to see real use case of QET.
175 2021-11-23 20:29:44
Re: Shortcut for hiding conductor labels (2 replies, posted in EN : Help, suggestions, discussions, ...)
You can set the properties "Show one text per folio potential" in the section "conductor" of project properties dialog and folio properties dialog.
