You have been assigned a bug task for a public bug by Jay (OpenERP) (jvo-openerp):
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 ** Affects: openobject-client Importance: Wishlist Assignee: OpenERP sa GTK client R&D (openerp-dev-gtk) Status: Confirmed -- field attribute readonly=True https://bugs.launchpad.net/bugs/378824 You received this bug notification because you are a member of OpenERP sa GTK client R&D, which is a bug assignee. _______________________________________________ Mailing list: https://launchpad.net/~openerp-dev-gtk Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-dev-gtk More help : https://help.launchpad.net/ListHelp
