I run QET on Plasma.
I normally have nine (3x3) desktops i can quickly switch between for different tasks.

I normally want program toolbars detached and placed at very top of screen, (most program top frame right part is just uninteresting grey area so let us use it!)  which means i get larger drawing area.

Problem: QET floating toolbars shows up on all desktops; also on top of other programs.

Workaround: I minimise QET before switching desktop.
 ( but that need one extra mouse click, oh, my...!   Other programs do not need be minimised for their toolbars not to show up on other desktops )

Anyway it is not looking polished and i was thinking maybe some developer know a quick fix to apply in QET, or for now maybe a setting user can do somewhere in Plasma?

@ Nuri: you really quickly changed that spelling nomicons/smile

I stumbled on a couple element in

QET Collection
  Electric
    All-pole
      Transformators (sic) and power supplies
        Transformers

1) the "Two winding transformer" have no Label. And what i enter as annotation and location end up at bottom of folio.

2) The "transformer with screen" element do have a Label, the element editor say, but works like 1)

I have not checked all...

Lets not post improvement suggestions on guillotine here then... nomicons/wink
- And that piece of invention is not one i am going to test on myself and feedback on !

scorpio810 wrote:
Morganol wrote:

What would be really nice is to have QET set variables of filename, path, time, date when opening and saving the file, Then they are easily made visible on document template both when editing and on pdf and paper print.

nomicons/blink  nomicons/blink 

mockup screens, how, etc...........

Better now? : https://qelectrotech.org/bugtracker/vie … d=111#c229

Thank you nomicons/smile
Filename of project of folio in view is now displayed in QET program window title - like is common in many other programs -perfect nomicons/smile


Screenshot from Plasma on Mageia 6.

[s]I just wonder why not show it directly but just after file have been edited?[/s]
[s](Think scenario you open a few projects to view for reference or cut/paste from)
[/s]EDIT: Now i see it is updated immediately, r4840 /EDIT

Nuri wrote:

But I not agree with the feature request of Morganol about the "save as" functionality: adding the project file name in the dialog would add more risk to overwrite an existing "good version" of a project.

Oh, i just meant as workaround: use the Save As button - because it is never greyed out.  It then opens the folder from which you opened a file and you can click a file to have that name filled in, and then i usually edit the rev number in end of filename;

I often save to new file names in an ever increasing number, like shema-01, shema-02, shema-03...

I once had a program where i could enable autosave, and it then upped that number automatically each time.

I would not like autosave in QET, but maybe a future idea could be to have Save As to automatically up a last number in filname if it exist (i.e my scanner software do that)

In case it is only one conductor in that net: for keeping properties of old conductor draw the new before deleting the old.

What would be really nice is to have QET set variables of filename, path, time, date when opening and saving the file, https://qelectrotech.org/bugtracker/view.php?id=111

Then they are easily made visible on document template both when editing and on pdf and paper print.

Another workaround is to use save as, and save to same file.

On the subject of saving, i cant see what file i have open; i see project name, but not file name anywhere.. am i not looking in the right place?

This is not only a bad thing; optimally it in future would be possible to choose.

I find QET is a bit mixed up in handning conductors like it was network / signals - it normally copies all, available info between conductors of the same network.

I think there would optimally be some network related fields that are copied (network name and type) but not conductor number/color and area.

Several conductors can belong to same network / signal, but at the same time the different cunductors need different identification.

Example, the network "L1" may be carried by black 4mm2 conductors in the cabinet, but in other side of terminal the conductor is a 6mm2 member marked "1" in a cable.  (and optimally the cable should also have a ID)

There can be different creative ways to document this, but I am a newbie in that and have not settled on a way to do it.
Currently i often write a description in a a short text instead of mocking with conductor labels, or i do a bit of both.

(Bookmarks: that clickable list that is possible to see for some documents in pdf readers.)

I am thinking of using ghostscript to add bookmarks to the pdf exported from QET, using this method i found now:
http://ask.xmodulo.com/add-bookmarks-pd … linux.html
It is use ghostscript to add a list of pages and titles from a text file.

I wonder if someone more fluent in this subject can help with a simple script to generate that list from the qet file... Something like

For each line starting with  <diagram indexrev=" , parse that line and:
   Start to output a line, starting with  [Page
   add page number retrieved from the order="" field (with space added to both sides of number)
   add[color=#3366ff] /Title ([/color]

   add the title retrieved from the title="" field
   add ) /OUT pdfmark and linefeed.

If we can automate that, including afterwards running the ghostscript command in a script it wild be really nice.

OK even better if integrated in QET of course nomicons/wink

I see the four bugs closed, and r4829 closing Bug 122 + memory leak, and r4830 closing Bug 118.

Six bugs (three causes) closed fixed in a day, great progress   nomicons/grin 

*If* the link bug was existent in r4805 you can probably close Bug 123 as well.

Thanks for the quick action now Joshua nomicons/smile

I confirm it fixed by r4828

You don't monitor the bug tracker ?

Could you now close bugs 125, 126, 129, 130 - I do not have such rights.

The other bugs there around i can not say is caused by the same reason, but maybe you can tell better from my screenshots and your knowledge.

Happy new year
/Morgan

For at least the recent few svn versions of QET:

For both folio references and master-slave, QET crash when saving if I do not unlink the elements before deleting them.

See  some of my bugs posted lately.

I also experienced QET crash when i clicked a xref link pointing to a deleted element.

Thank you for the explanation nomicons/smile

In don't understand this:
This morning i opened a terminal in the checked out folder, and issued "svn up" and it replied it is updating "." and it is on 4823.
Now in same terminal i again issued "svn up" and it replied it is updating "." and it is on 4824.
So it did not update any file, yet it say it is next revision number??  What is wrong here?

I totally agree: draw inactive state, and name PLC connections to what they do when active.

Problem comes when i link the opening and closing coils (slaves) on the electric shema, to the 5/3 valve on the pneumatic shema.  (self made elements, see my prototypes at bottom section of the shematic in picture at https://qelectrotech.org/forum/viewtopi … 571#p5571)

Like the PLC signals the active state and connection is named thereafter, similarly I think the best it to have this set up so the coil that makes the pneumatically controlled processvalve open (=media flows) at the master (the 5/3 control valve) is given a symbol meaning open (=media flows) Easy and clear so far.

Problem comes now: QET is targeted electrical, so at the master is shown symbols for open and closed switches.  By switches switch that is letting current through is called "closed" - opposite from the valve.  My current thinking is that for such application i describe here, i should make it show "closed" switches (ON = let current = media through) for the pneumatic coils that open the process valve.

That, for me, seem logical in sense of ON/OFF, it is just the traditional closed/open nomenclature that is illogically inverse in fluids contra electrics, and it is quite disturbing.


( I can dream of a more configurable function i QET so it can show other symbols instead of switches, or words that show up at both slave and in master xref tble, but this way i think i can use what we have )

This is nothing about QET, but a general problem i often face:

When a valve let media pass, it is OPEN, when it stop media it is CLOSED.
When a contact let current pass, it is CLOSED, when it stop current it is OPEN.


That makes it a pain to describe and read electric + pneumatic shemas and description in english.

I have to think in terms on and off: wehn a switch or valve conducts they are on ON, when they stop media/current they are OFF.

So when creating master / slave elements for pneumatics, i let a NC normally closed switch represent a NO normally on valve (both hare ON)

That is OK as long as i draw it.  But when trying to explain it i text it get easily weird, you do not say a valve is "ON" in technical texts.. or?...

Brain hurts...

How do you other people think and solve the nomenclature to make it clear?

Ah, thanks

Yesterday I checked out svn version 4817, svn said

svn checkout svn://svn.tuxfamily.org/svnroot/qet/qet/trunk mynewfolderforit

and command "svnversion", and "svn up" say i am on 4817.

But according to
https://svnweb.tuxfamily.org/log.php?re … mp;isdir=1
latest is 4814 , so some updating of that page is broken?

OK
(...and BTW it is the same when i make own terminal elements with more pins.)

There are some terminals in
/elements/10_electric/10_allpole/130_terminals&terminal_strips/90_terminal_strips_diagram/

I believe the intention is to replicate conductor properties between all ports on a terminal.
But depending on what conductor you edit, the T and X terminals fail;

T: The middle terminal is not updated when any other terminal is changed.
X: Depending on what terminal you change, one or two of the other terminals is not updated.

In the attached screen shot i set name on the selected conductor.  It propagates to some conductors but not to the conductors leading to F10, F11 nor F14.

I guessed it was the same...  Sounds like much work
At least, it happens seldom now since you worked on it above, and i have never seen it happen for conductor deletion since that  nomicons/smile

Above was seen in r4804 and earlier.
I see now comment for latest revision 4805:

Element : change freeze label variable from a string to a bool.