Search options (Page 4 of 12)

Never been in this land before... I just read your note above and added option like in image below, but i get result:

***Unknown option -std=c++1y
16:57:50: The process "/bin/qmake" exited with code 1.

[color=#333333]
What can i try?[/color]

@ 4901, Quick check: It crashes immediately on opening a drawing
- even a brand new drawing now created with it, place one element, save, close, open -> crash

OS: Mageia 6, 64bit, Plasma

Do you want me to check something specific?

Maybe i just try to cram unusually much into one page...

EDIT, add:
Just to describe how i use it for my so far third project in QET:
Most of the time i do other things: program PLC, source parts, manufacture special cirquit board, some mechanics, lead project.

Then i occasionally fire up QET to adjust the drawing: add some info, backannotate from real world, rearrange something, and bam - i have many erroneous connections if i had forgotten to shut of automatic connections.
-Thank you for the undo function! 

That does not change the default state...

Good thoughts.  An idea: when a slave get disconnected from a master, change its name like this: Prepend "former:" before the name, so it becomes i.e "former:K43"  Then it is easy to find when connecting to new master because the designer often remember what it was before (and of course like before make name identical to master when reconnecting)

@ Captaindoc: see https://qelectrotech.org/forum/viewtopic.php?id=997

https://qelectrotech.org/bugtracker/view.php?id=135

Ah, thanks Nuri for explanation.     Note to myself: try google translate next time
And Joshua for the development of course

The suggestion of Nuri could make it require less width and leave more space to drawing, i like that.  (now i use google translate...)

To that i would add: Move the title column leftmost, because that is the widest but most often we do not need to read the whole title so it can be visibly cut without usage problem.

No: because the designer (i.e me) can make that setting before sending the documentation (project file)

The customer (i.e electrician or machine user) only have to install QET and open the file and it will be write protected.

No need for me to tell them how to set something in a program they heve never used, and maybe they will forget to do it anyway.

IF they want to save changes they can search for (i.e phone me) and change that checkbox

IF i forget to set it write protected i can phone them and guide them to do it, or send a protected file.

EDIT:  Plus this solution do not affect the saveability of other project files - as it is per project and not QET global.

That was lightning quick thanks

IMO, No password etc please, i dont understand why some programs add that, there are lots of standalone and system integrated encryption and validation functions around...

Yes write protect is better than nothing (it is easy for user to write protect a file in linux, but unfortunately maybe not yet easy in other OS - yet!)

One problem with solution in 4873 is that user must remember to enable the function before accidentally saving over the original.

Could it be placed in project properties instead?

It need some clever logic then to be able to save the original with save disbled. Pseudocode:
At save request:
 IF that flag have been changed since file was opened: allow save
 ELSE read the flag to see if save is allowed.