Hello Don Kirkby,
It has been fixed in
~openerp-dev/openobject-client/trunk-dev-client and it will merge soon with
trunk client. thank you for report and patch
here could not apply your patch because it's break consistency
between one2many and parent record deletion.
Thanks
--
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/701298
Title:
Deleting a new, unsaved record causes ValueError
Status in OpenObject GTK Client:
Fix Released
Bug description:
Here's a detailed description of one way to cause this error:
1. Create a new database with sample data and any profile. Complete the
installation.
2. Go to the Partners screen and click the New button to create a new partner.
3. Type "Foo" in the Name field.
4. Click the Delete button.
5. A dialog box appears, "Record is not saved ! Do you want to clear current
record?" Click the OK button.
Expected behaviour:
Either all the fields are cleared back to default values, or the screen loads
an existing partner and takes you out of the "new record" mode.
Actual behaviour:
None of the fields change value. An error appears in the client error log:
Traceback (most recent call last):
File
"/mnt/workspace/don/openerp-bzr/client/delete-new-record/bin/modules/gui/main.py",
line 1334, in _sig_child_call
res = wid.handlers[button_name]()
File
"/mnt/workspace/don/openerp-bzr/client/delete-new-record/bin/modules/gui/window/form.py",
line 263, in sig_remove
id = self.screen.remove(unlink=True)
File
"/mnt/workspace/don/openerp-bzr/client/delete-new-record/bin/widget/screen/screen.py",
line 507, in remove
idx = self.models.models.index(self.current_model)
ValueError: list.index(x): x not in list
I am testing this with OpenERP 5.0.15 running on Ubuntu 5.0.15.
_______________________________________________
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