With automatic line wrap i mean a long text without linebreaks is dynamically broken into several lines depending on available width.

Example, if the above sentence is put into a cell with limited width:

With automatic line wrap i
mean a long text without
linebreaks is dynamically
broken into several lines
depending on available width.

That would make it take less work to dump informative texts onto drawings with less manual work to manually break them.

Great videos nomicons/smile

Than you Nuri for quick and well written information nomicons/smile

Nuri wrote:

First, i am not sure how all variables in folio properties are intended to be used.

like you did in your screenshot nomicons/smile

Then it is like i want it to be already nomicons/grin

Nuri wrote:

Do we have some description of the concept/idea?

No, these concepts are pretty new (only in 0.51 devel) and were developped by Davi.
See here for more informations:
forum topic
There is an online manual but it's not finished and it was written for QET v0.4.
For sure, it would be nice to explain the variable concept in the online manual.

That forum topic link do not work...

I like that manual. I think it is well designed and written.  It "just" need to be extended and updated...  by someone having the time

Do we have some overview of what variables can be used where and when and when they are defined where?

no, not at the moment. If you have some ideas how this could be shown in the GUI, please explain them.
I think we need to integrate in the GUI some URL to the online manual to automatically open in a web browser.
It would be the easiest way to keep informations up to date. But the online manual must be written by some people how can correctly write in english...

I see there are already short explanations here and there where variables can be defined and used.
IMO, you should keep those short explanations there, (make sure they are complete and correct, but short) and every such place link to a chapter that carries full information; beginning by why, concept, how to use by simple example, then a table(?) listing all variables and where they can be set, then listing or explaining where they can be used.  And some syntactic how they can be combined, what characters are legal, etc.

It would be good if manual could be installed locally, by distro package or manually downloaded and uncompressed some specific place that works with those links.  Not everybody have internet access always. 

I also have not understood what a "Reports folio" is

They are the arrows to interrupt a conductor that is continued on another folio. In my opinion, "reports folio" is not a good translation. Some proposals?

Ah. I completely misunderstood that naming. ( To me it sounded like some report that can be generated onto some page. )

Why not use the naming "Sheet referencing" as that is already how the element section is named that contain the linking elements
p, li { white-space: pre-wrap; } Chemin de la collection : common://10_electric/10_allpole/100_sheet_referencing
Chemin dans le système de fichiers : /usr/local/share/qelectrotech/elements/10_electric/10_allpole/100_sheet_referencing

I also have seen them named "ports", "off page connector", "signal flag" and such.  I think "port" is short and tells what it is, while "sheet referencing" tells what it does.. so ...  "sheet referenced port" tell whole story but is too long...   ... whatever, just use *same* name everywhere  IMO, and ask whoever set the original name about it before changing from "Sheet referencing".

...To say it short: change "Reports folio" to "Sheet referencing" - few changes, much better to understand.

EDIT: "Label of report folio" -> "Label of Sheet referencing symbols"  /EDIT

I am not sure how Folio is intended to be used

by default, QET can only number folio in a continuous way (1, 2, 3, 4...)
If you want something else, you can write the folio number in the field "folio" and check the option "Use labels of folio instead of their ID" in the QET settings window.

OK.
It seems i can also there write a short name for a small part of the system, have that same short name for more than one page, and to differentiate the pages in the inset, i can there use variables directly in that template: %folio-id(%folio-total)

BTW, how do i make the .qet file name show in title blocks?

type it by hand! There is no function that automatically writes the file name in it.

IMO, there should be a variable carrying the file name, and be usable in the title block

I often save many slightly different versions of my work, differentiated only by some number at end of file name.
Both when sketching different design solutions, and/or different ways to divide it onto pages
... and/or using software that crashes nomicons/wink

Actually, I push it back to you nomicons/wink

Here is part of output when running sudo make install:

cp -f -R /home/morgan/Hämtningar/qelectrotech-trunk/ico/oxygen-icons/128x128 /usr/local/share/icons/hicolor/
cp -f -R /home/morgan/Hämtningar/qelectrotech-trunk/ico/oxygen-icons/256x256 /usr/local/share/icons/hicolor/
sh man/compress_man_pages.sh
gzip: man/files/be/man1/qelectrotech.1.gz already exists; do you wish to overwrite (y or n)? y
gzip: man/files/man1/qelectrotech.1.gz already exists; do you wish to overwrite (y or n)? y

etc, etc...

As seen, your script uses -f force flag with the cp operations.
Then it starts man/compress_man_pages.sh which runs gzip, but without force flag, so it asks user.

This is the gzip calling line in that script:

find ${MAN_DIR} -type f -name "${APP}" -exec gzip -9n {} \;

I suggest to add -f to gzip in that line, so it force writes like the rest of install script execution do.
Or is there some special case you do not want to update the man files automatically?

...Even better if i know how to use them nomicons/grin

First, i am not sure how all variables in folio properties are intended to be used.
Do we have some description of the concept/idea?

Title
File
Folio
Plants
Location
Index Rev

And i also see some other variables can be put in those fields, and the results from those fields used as variables in i.e title blocks.

Do we have some overview of what variables can be used where and when and when they are defined where?

I also have not understood what a "Reports folio" is. When is it generated, and how?

I played with the "Label of report folio" field and raised my hands in joy \o/ as it suddenly happened what i was about to ask for: I want the sheet referencing labels to show not only page number and coordinate, but also a short name of that part of equipment.

Just playing along for now, i entered %M_%LM_%F_%f-%l%c, and the result is as per screenshot below.
That is a bit overloaded, i probably only want to use Folio or Location ( plus _%f-%l%c ) in sheet referencing.

I am not sure how Folio is intended to be used i guess i can have several pages with same Folio value? ( i.e several pages for same electric box )

I am thinking, maybe there should be separate fields to enter formulas for sheet referencing label, respectively "Reports folio" whatever that is?

BTW, how do i make the .qet filename show in title blocks?

Nuri wrote:
Joshua wrote:

but this appear only with conductor so "it's a QET bug"

and with basic shapes too!

I have not seen that... yet... i think.
You mean when deleting lines, rectangles etc in schema editor, they have happened to become "ghosts"?

Joshua wrote:

I can now reproduce this bug and it's a big step.

Great.  Much easier to find then, even if I understand it is still hard.

Sorry you wrote that very clear indeed in the first place.nomicons/angel
I must get some coffee before engineering something today...!  nomicons/dizzy

@developers

The bug behaves differently on different systems despite using same svn, and same file and procedure.
(i can repeat also on 4751, both standalone compiled and when running in debug mode from QtCreator)

So bug is dependant on build environment and/or where it executes.

If you want to try changing something i can try here immediately to see if it makes a difference.
Maybe there is some optimisations that can be switched off, or forcing to use more rigid but slowing options in compile?
Do it really initialise everything needed, always?
Or you maybe can flip some compile settings?
Or can you put in some kind of trap or logging feature explicitly to trap what happens when I perform the operations that trig the problem i see here when i follow the procedure described in the bug?

Thank you Nuri for investigation and knowing the scale 1 grid dot = 5px
I made a feature request https://qelectrotech.org/bugtracker/view.php?id=109

Hm, i still have not found a way to make text autowrapping in qet, but I am no HTML wiz.

I can make a one cell table with long text that wrap when i open it in web browser, but it do not wrap in QET, it just expands... even out of folio...

How do i tell it a max width?

Now I experienced that for new version of qet despite first issuing sudo make uninstall, it asks for overwrite when running sudo make install.
Hmm... maybe i should run make uninstall *before* compiling the new version?

(issuing sudo make install again on already installed version do not make it ask for overwrite, but it also do not list any lines starting with gzip)

@Nuri

1) Strange! I repeat it every time, also with slight change in procedure, and also trying to follow you exactly (you use slight different position of valve and deselect conductor before drawing new - also when i do that here it fouls up.  What QET version, Qt, version etc.. do you compile locally?  Other difference?  My system is described @bug 107.

If you find some method to repeat the fault (any file or procedure) i will try here.

2) Regarding the sloped conductor i think it is a variant of bug 105 i reported, and i can repeat that exactly like you on this drawing too.   - could you add a comment and link to this video there please?   This .qet is a sister clone of what i used for that bug.  The pump from where the conductor is slanted is the same home-made .element.  I wonder if there is some oddness about it, like unusual placement of connector?

HOORAY nomicons/wink
By this method i can make it crash quickly and repeatable
https://qelectrotech.org/bugtracker/view.php?id=107

Yes it would be nice to be able to make a simple and reliable "how to reproduce" procedure the developers can use to track this down.

I am getting closer, but it seem stil rather random...

I caught another kind of crash: when selecting an area
https://qelectrotech.org/bugtracker/view.php?id=106

I have been trying to make a repeat instruction but it is not easy.
I found minor repeatable problem though, https://qelectrotech.org/bugtracker/view.php?id=105

1) Tanks tor changelog links.

2) For bug tracking i agree not close until confirmed, but IMO it is good practice to update issues with a short note like
"we now made this change, see changelog URL xxx, hope it helps but not certain, so leaving bug open for a while"

3) Oops, i forgot to twist my fingers!

Running r4748 in qtcreator debug

I know that i never did a group delete this time.
I may have deleted some element.
I know i have deleted some conductors, especially the inferior one.

See image: at bottom there is a fat black conductor.  I never made it fat.  It was a normal default thin connector.  A while after i had group moved some elements around that conductor, i noticed the conductor right vertical part was touching the dotted oval, so I grabbed that part and dragged it left.

But it did not follow nicely, instead the top part was still sticking out at right like in the picture.  I then deleted it and made a new.  At that time it looked like old one was gone, and only the new one visible (In this screen-shot you see the right vertical part of the new conductor slightly left of the old (fat) ghost conductor.

The old ghost get visible when i select the area.

Then i realised it may be this bug again, saved and yes it crashed.

No source file visible, just disassembler.

qtcreator "Application output" window displays:

QXcbConnection: XCB error: 3 (BadWindow), sequence: 34898, resource id: 43994263, major code: 40 (TranslateCoords), minor code: 0

...And then saves and exports every page, then:

pure virtual method called

terminate called without an active exception

EDIT: that code formatting function in this forum posting is a bit buggy, at least here on current Firefox... /EDIT

EDIT2: That ghost line shows in image exactly like when hoovering mouse over a conductor, but this is without hoovering the mouse over that ghost.  /EDIT2

OK, thanks... according to that discussion in that link "make install" is supposed to overvrite as i guessed, but when i make install qet, it seems like make fail to tell gzip to overwrite without asking?

This maybe is something that could be improved in your make recipe but i dont know these things and you have other things to do.

The easy workaround is of couse to issue make uninstall first, or just answer those overwrite questions manually.

Thank you for explaining nomicons/smile

Great, thanks nomicons/smile
Iĺl start there.
Seems i need to browse through your videos better.

Ah.  OK it seems it sometimes works to not uninstall first, but best to always do that.

BTW i see it put things in /usr/local/man/
That folder did not even exist on my system before installing Qet

Programs i have use /usr/share/man/ for similar stuff, and so do the Qet 0.50 mageia rpm package
One odd program use a third alternative /usr/local/share/man

All three are used by the system
# manpath
/usr/local/man:/usr/local/share/man:/usr/share/man

But if you want to adhere best to filsystem standard i think you should change to usr/share/man/
http://www.pathname.com/fhs/pub/fhs-2.3 … ANUALPAGES

Maybe i can edit the text in source mode.

Maybe use a "table" of one cell?
Ore some other trick...
I am not used to HTML, but surely can read up on it if that is a solution.

But how is actual total width defined?
How big is a "px" or whatever measure is suitable

Yes nice nomicons/smile
Are developers waiting for some confirmation, or why are the bugs not updated?

I see i already run r4741 now
Is there some changelog viewable (good for us testers to see what to eventually test)

Ah, I misinterpreted your "#100 -> #104 "

I can still repeat bug 101 completely following my instructions there, for all three variants A,B,C.
https://qelectrotech.org/bugtracker/view.php?id=101
Does it work OK for you?