Clicking a button in a form view brings one-to-many widgets back to the first record
Bug #1072784 reported by
Numérigraphe
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Odoo GTK Client (MOVED TO GITHUB) |
Fix Committed
|
Undecided
|
OpenERP Publisher's Warranty Team |
Bug Description
In v6.0 and v6.1 at least, when using a form view with a o2m widget, if you click a button, the o2m widget is reset to the first record.
This is particularly annoying when you have more than 10 records in the o2m list, and you want to click a button on each of them.
The attached screencast illustrates this. Please note that the problem also happens when you click a button on the "parent" form.
Lionel Sausin.
Related branches
lp://staging/~numerigraphe/openobject-client/6.x-o2m-focus-reset
Ready for review
for merging
into
lp://staging/openobject-client/6.0
- OpenERP Core Team: Pending requested
-
Diff: 68 lines (+19/-3)4 files modifiedbin/widget/model/record.py (+1/-1)
bin/widget/screen/screen.py (+2/-2)
bin/widget/view/form_gtk/one2many_list.py (+1/-0)
bin/widget/view/list.py (+15/-0)
Ready for review
for merging
into
lp://staging/openobject-client/6.1
- OpenERP Core Team: Pending requested
-
Diff: 68 lines (+19/-3)4 files modifiedbin/widget/model/record.py (+1/-1)
bin/widget/screen/screen.py (+2/-2)
bin/widget/view/form_gtk/one2many_list.py (+1/-0)
bin/widget/view/list.py (+15/-0)
Ready for review
for merging
into
lp://staging/openobject-client
- OpenERP sa GTK client R&D: Pending requested
-
Diff: 68 lines (+19/-3)4 files modifiedbin/widget/model/record.py (+1/-1)
bin/widget/screen/screen.py (+2/-2)
bin/widget/view/form_gtk/one2many_list.py (+1/-0)
bin/widget/view/list.py (+15/-0)
Changed in openobject-client: | |
assignee: | nobody → OpenERP Publisher's Warranty Team (openerp-opw) |
tags: | added: maintenance |
Changed in openobject-client: | |
status: | Opinion → In Progress |
To post a comment you must log in.
Hello Lionel,
Thanks for sharing the video with us.
The reason why this happens is, when you perform any action on o2m widget, the parent record is reloaded and in turn the child is reloaded too, that is why the o2m is reset to the first record.
Parent needs to be refreshed in case when the result of any action is to be reflected in the parent record itself.
Considering the case of `Manufacturing Orders`, there are two o2m, `Stock Moves` and `Consumed Products`. When you process the stock moves, they are moved to `Consumed Products`. Here, to move the component on the fly to consumed products, parent record needs to be reloaded.
This bug needs discussion from the experts, so I request the experts to share their opinion on this topic, meanwhile, I am changing the bug status to `Opinion`.
@experts: would you please share your views on this.
Thanks.