Thanks for making the behavior clear Anup.
Is this documented somewhere? I think this priority thing is worth mentioning
in the doc.
Also, please let me disagree in that "states attribute (...) get higher
priority than xml attribute" is the correct behavior.
Wouldn't it be more useful to "or" all the possible readonly directives, rather
that give priority to one or another?
In the current state, "readonly" in views is much less useful.
Lionel.
** Changed in: openobject-client/trunk
Status: Invalid => Opinion
** Changed in: openobject-client/5.0
Status: New => Invalid
--
readonly="1" in views does not work when object state makes the field
readonly=False
https://bugs.launchpad.net/bugs/645172
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
Status in OpenObject GTK Client: Opinion
Status in OpenObject GTK Client 5.0 series: Invalid
Status in OpenObject GTK Client trunk series: Opinion
Bug description:
When a field has a "states" attribute that makes it writable, you can't make it
read-only in a view by using the XML attribute readonly="1".
Lionel
_______________________________________________
Mailing list: https://launchpad.net/~c2c-oerpscenario
Post to : [email protected]
Unsubscribe : https://launchpad.net/~c2c-oerpscenario
More help : https://help.launchpad.net/ListHelp
