[6.0] Sorting a column discards changes on the one2many_list (usability bug)
Bug #601791 reported by
Borja López Soilán (NeoPolus)
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Odoo GTK Client (MOVED TO GITHUB) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
On the 6.0 GTK client, clicking on a column header, will cause the reload of the one2many list (sorted by that field) even if its contents have been modified. So, each time an the user clicks on a header by mistake (easy if you have one 'editable="top"' list), the unsaved changes are lost.
The GTK client should ask the user if he really wants to save the record [if modified] before reloading the one2many ("This record has been modified, do you want to save it?")
Revision history for this message
| Ravi Gadhia (OpenERP) (rga-openerp) wrote | #1 |
| Changed in openobject-client: | |
| status: | New → Fix Released |
| Changed in openobject-client: | |
| milestone: | none → 6.0 |
To post a comment you must log in.
hello Borja López Soilán
It has been fixed by revision 1517, <email address hidden>
thank you