Please let me reopen this bug to emphasize that the current behavior is not consistent: - when you create a new record from a form view, the buttons are active: when pressed, they save the record and run the button's action - when you create a new record from the form view of a o2m field, the buttons are inactive: you need to save the parent record to make them active - when you edit an existing record from the form view of a o2m field, the buttons are active: when pressed, they save the child record (but not the parent) and run the button's action Lionel Sausin.
-- You received this bug notification because you are a member of OpenERP sa GTK client R&D, which is a bug assignee. https://bugs.launchpad.net/bugs/708631 Title: Inconsistent button activation between forms and o2m forms Status in OpenERP GTK Client: New Bug description: The current behavior of the client is not consistent: buttons do don't get activated the same way depending on whether you create a record from a plain form view or a o2m's form view (see comment #2). Examples: Go to Sales -> Address Book -> Customers Select a customer Activate the "History" Tab on the notebook Create a new entry for the Phone Calls o2m. You can see that the buttons are disabled but they should not because the state is "open" and thus those buttons should be enabled for this state. Other examples can be found in duplicates of this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/openobject-client/+bug/708631/+subscriptions _______________________________________________ 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
