When _sign is negative, it doesn't select the first column but the second. So
despite of selection the wrong column, it could crash if there is only one
column in the view.
review3241004
(transplanted from f05cc122d3fd52141386f8097d0fc3989b85abd4)
False is not always a good valid value for the field, so it is better to let the
field dealing with default value.
issue3643
review3281002
(transplanted from 9a16381241f48ca880e7544edeef54c255c99255)
It should use the text filled in the search entry.
And it should not close the window if nothing is found.
review3101003
(transplanted from 8b22f7366f7caeb7ecbe86c28b8b4f8f3bf32627)
Since 2.6, reference field can be used in One2Many so in this case the value
should be forced like for Many2One.
review2581002
(transplanted from 67acb340ba7caf7f6c801e2c7af6884e6603b614)
A wizard could be launch by a button defined on a children record. In this case,
the ids to reload is not the ids from the wizard as they are from the children
model but just the current record.
issue3519
review2571002
(transplanted from 6f657eeefffcc5a74be70e7cc8868fc7293d3c44)
It fixes also a strange behavior of GTK that doesn't display any images if the
icon is changed before it is realized.
issue3191
review1451002
(transplanted from 4bc44691dc89dfd7802c9d84bbb466f98038bb75)
By deactivating the button, the button lost the focus which makes NoModal
selects the wrong sensitive widget and thus the wizard behaves like if it was
launched from the menu instead of from a tab.
issue3353
review1083003
(transplanted from 0d135623d016ce2d8185fcb5790eb22d9d8de254)
The conversion of a domain into string should keep the same significant digit,
which means to not use the field digits definition but significant digit of the
value.
issue3266
review1041002
(transplanted from add046625334e0237bc6fc9d684427e6de1b1903)
When I delete some records of an one2many-field in an on-change-Event, the
deleted records are sent to the client and the client hides them in the list.
Pressing the save button the record loads again including the deleted o2m-records.
The reason is the force_remove-flag. This will delete the record on the
client-side and therefore this change will not be reflected on the server side.
issue3091
review744002
(transplanted from e40190b28b312f3dd63bceb167698a885826ea0e)