c2c-oerpscenario team mailing list archive

["nch\(OpenERP\)" <nch@xxxxxxxxxxx>]

I would like to revert back the commit for the comment #4 as this may cause a regression because now the user will not be able to close the dialog box at all if he has atleast 1 required field. say for eg: you need to create a sale order line and 
you click on new to create new record the dialog box pop ups now you change your mind , you do not want to create a new record and you press cancel to close the dialog box but you want be able to close it until and unless you fill in the required field.
I am marking this bug as invalid. according to the architecture does not seems to incorporate such changes.


Thanks,

** Changed in: openobject-client/trunk
       Status: Fix Released => Invalid

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
https://bugs.launchpad.net/bugs/539722

Title:
  Close button remembers changes

Status in OpenObject GTK Client:
  Invalid
Status in OpenObject GTK Client trunk series:
  Invalid

Bug description:
  When you use the close button to close a separate window (sale.order.line and similar) it remembers changed data, if that object already existed.

Example:
Create a new sale order and add one sale order line, press ok to add this new sale order line to the sale order.
Now edit that same entry and make the description (or any other required field) empty, and press the close button.

If you now edit that same line the description will still be empty. So it won't validate unless you fill it in again.

Running the client with log-level=debug_rpc_answer shows that pressing the close button doesn't trigger any event.

The behavior I think I should be seeing is that it asks me if I want to save my changes. At least that's what I see in the handling of the close signal in the client code.

Using OpenERP 5.0.7 (both server and client).