c2c-oerpscenario team mailing list archive

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

This is acceptable, butc sorry, we cannot introduce this in 6.0 currently.
Thanks.

** Changed in: openobject-client
       Status: Fix Committed => Confirmed

** Changed in: openobject-client
   Importance: Medium => Wishlist

** Changed in: openobject-client
     Assignee: Christophe Chauvet - http://www.syleam.fr/ (christophe-chauvet) => OpenERP sa GTK client R&D (openerp-dev-gtk)

** Changed in: openobject-client
    Milestone: 6.0 => None

-- 
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