Labels - Default as Non-Editable?!

[d.healey]

@DanH I pretty much only use labels to get user input. If I need to display text for "labelling" purposes I include it in LAF or paint routines.

[DanH]

@d-healey Ok well for us old school lot it's worth a shout

[ulrik]

@DanH said in Labels - Default as Non-Editable?!:
Anyone else in favour of the button being off by default?!

Yes, agreed!

[Lindon]

@DanH said in Labels - Default as Non-Editable?!:

I don't know if anyone else suffers from this but I quite often overlook turning off the editable button for a label and have to run all the exports off again... Anyone else in favour of the button being off by default?!

if you mean labels not buttons, and default is editable = false, yep Im all in.

[CatABC]

@Lindon +1

[Christoph Hart]

-1 here, it will break existing projects because the XML strips all default values to keep the file size in check so all editable labels will then be read only.

I also find it mildly inconvenient, but the annoyance isn't worth the backwards compatibility break or adding a preprocessor flag.

[DanH]

@Christoph-Hart out of interest where is it in the source code? Happy to change it for my own use

[d.healey]

@DanH just search the source for the property name and you should find it pretty easily.

[Lindon]

@Christoph-Hart said in Labels - Default as Non-Editable?!:

-1 here, it will break existing projects because the XML strips all default values to keep the file size in check so all editable labels will then be read only.

I also find it mildly inconvenient, but the annoyance isn't worth the backwards compatibility break or adding a preprocessor flag.

yep get what you are saying, however the compromise would be on label creation, it starts as editable=false

So when I make a new label (in future) the editor adds it with editable=false, so now it behaves like a label, and if I want to change it to some sort of text entry box then I have to go change this value. This I think gets rid of 99% of the problem and retains backwards compatibility

[DanH]

@d-healey ScriptingAPIContent.cpp :thumbs_up:

[d.healey]

@DanH Yeah that looks right, but I just tried changing it to false and it also affected labels that are already on my UI...

[DanH]

@d-healey as in set all the labels in the opposite direction?

[d.healey]

@DanH It set editable to false on all of them, old and new.

[DanH]

@d-healey oops

[DanH]

@Christoph-Hart ok perhaps a middle ground is to have an icon next to every label in the Component List that shows if it's editable...

Just found some more and now have to spend a couple of hours running my last update off again

[Lindon]

@DanH no the middle ground is to leave everything the way it is - but for all new label widgets to default to off.