I don’t get the behaviour of a forms with fields if I try to make them dynamically editable/non-editable.
I need to make fields dynamically editable/non-editable. It seems, to accomplish this, I have to set the (design time) property “editable” checked. With that setting I can use on forms level the forms.ScoSubjectSections.controller.readOnly = false/true; command or on field level elements.fldCode.enabled = false/true;
But these commands don’t work if the fields have the property “editable” unchecked.
It would be much easier for my case to set the field property “editable” unchecked and make the field editable if desired. Is this somehow possible?
The reason I want to do that is that the fields are usually read only except if a new record is created. So starting in read only mode would save some methods/code.
I understand your point (had/have the same). But when inserting new records it’s a conceptula weigh up between having a (dialog)form for each data entry (our old app) or entering the data directly into the existing form (what I try out now). So either way has its (dis)advantages
By the way, to avoid that editable changes the background colour, just give the CSS field style the same color as the background (on Mac the light blue colour for the selection part) and make the field non-transparent. Then there is no colour change when editing.
Regards, Robert
IT2Be:
Hi Robert,
I normally use readOnly. That works fine (for me anyways).
The reason for that is that I don’t like the fact that editable changes the background color of a field.
I know about the css thing (obviously) and use that as well but for some reason I just like readonly best.
Call it the mystery of the human mind if you like
IT2Be:
I know about the css thing (obviously) and use that as well but for some reason I just like readonly best.
Call it the mystery of the human mind if you like