This is how you can test it: create these boolean fields: Post Fax Other and one character field: Info - this one gets set to read-only when Other is NOT selected
Also, the three booleans act like radio-buttons, only one can be selected at a time. So when one gets selected, the on-change events de- selects the others. This works: click Post, then click Other. Result: Post gets de-selected, Other is selected, so Info becomes writable. This doesn't work: click Other, then click Post. Result: Post gets selected, Other gets de-selected, but Info STAYS writable. -- on_change events on a field used in an attribute https://bugs.launchpad.net/bugs/664515 You received this bug notification because you are a member of C2C OERPScenario, which is subscribed to the OpenERP Project Group. Status in OpenObject Addons Modules: Incomplete Bug description: If you have a field readonly when state == draft and you use an on_change event on a different field which then changes the state, the readonly attribute doesn't get evaluated. ie. in draft state the field transaction# is readonly. During an on_change event the state gets set to open but the transaction# stays read-only on the screen. _______________________________________________ Mailing list: https://launchpad.net/~c2c-oerpscenario Post to : [email protected] Unsubscribe : https://launchpad.net/~c2c-oerpscenario More help : https://help.launchpad.net/ListHelp
