c2c-oerpscenario team mailing list archive

["Jay \(OpenERP\)" <jvo@xxxxxxxxxxx>]

GTK team,

Please refer bug 426676 as well. This could be a server side issue,but
needs a client side support.

Thanks.

-- 
field attribute readonly=True
https://bugs.launchpad.net/bugs/378824
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: Confirmed

Bug description:
readonly=True (in py and xml) does allow programs to write but not to save the field.
onchange triggers can write into "readonly=true" fields, but this information is quietly lost during save 

Example (abstract)
onchange(qty,price)
returns value=qty*price
value is a database field.

it seems to me that readonly=true should only prevent user input.
and that onchange is considered as "user input"

how should a readonly field be filled if neither user nor program can set a value?
may be I am missing something.

may be an attribute "enterable" =false (default true) could prohibit user input and allow program input

http://doc.openerp.com/developer/2_6_views_events/views/design_element.html
just says "read only"

thanks