* ir_actions_common should return a deferred : some widgets
do not return a deferred in start, so it could be undefined.
it now is always a deferred.
* add icon for diagram view + breadcrumb support. diagram view
is so rare that it wasn't tested in the client refactoring.
This patch adds an icon for diagram view, and better support for
breadcrumbs
* add warning in debug mode print workflow: when no record is
selected, display a warning instead of failing silently
the method prepare_dropdown_menu wasn't called when the searchview did
not have an action id. This can cause problems in some cases (for
example, a crash in messaging when toggling the favorite menu)
in form view, the header height was higher than in other views (4 extra
pixels). This was caused by the floating buttons in
.oe-view-manager-buttons. This commit forces the column to take exactly
30 px regardless of its content. (it is not a problem even if the
content takes extra lines)
The previous viewmanager (before its refactoring in sept/oct 2014) was
ignoring some promises in its do_load_state method. The refactoring
actually fixed that, but of course, some other code was dependent on
the broken implementation. This commit removes the use of promises in
do_load_state, which is functionally equivalent to the previous code.
As a result, it relies on some subtle timing of the creation and
initialization of various views. It is somewhat fragile, but it is
actually what the former code did, only in a more explicit way.
See issue #3964 for more detail. Main problem was caused by commit
f0e331e005. It set the key name+'__display' to false when reloading
a record for all field types, but it was only concerned with many2many.
This fix is related to c12a2e1d16
Mutex allow to wait sequentially for mutex
Besides, if one of the onchanges deferreds fails, it does not resolve the mutex until all deferreds of the mutex are resolved.
Besides, we now wait for the onchanges mutex between each field commited value (line 596) in case the commited value leaded to a new onchanges, that we should wait for before commiting the rest of the values.
In multi company environment, the company logo was not updated on company change in the user preferences
This disrupted the end user, as he might think the company change did not happen.
One2Many fields can specify sub tree and sub form view, to be used when
displaying a list view and when adding/editing an element. Many2many
can display a sub tree view, but ignore sub formviews. This can be
fixed by specifying an alternative_form_view to the popup form widget.
Fixes the issue #1216 (follow the link for more information). The issue
was caused by a hack in list view: the magical suffix __display is used
in render_cell to determine if a many2many field should be updated. This
commit simply makes sure that old many2many fields + __display keys are
cleared.
A better way would be to redesign/refactor the list view to avoid that
hack in the first place. But this would be a much more complex task.
The issue is that when a default searchview is requested, it is
initialized without its view_id. Result: debug mode can't edit the
search view. This commit makes sure that when the field_view_get is
received, the correct view_id is set.
removed js that let user to uncheck radiobutton and from addons removed radiobuttons used for not required field except sync_typ.
changed this field as required because of functional requirement
This commit fixes two issues with debug mode:
* when a default searchview is requested, it is
initialized without its view_id. Problem is that it prevents debug mode from editing the view.
* add xml_id in Edit action form view(debug mode) : this makes the xml id visible in form view
Problem was that when the user types quickly in the search bar and press
enter, the keydown event of the enter key happens before the keypress
event of the last key entered. This means that the autocompletion has
a wrong string. The fix is to move the enter selection detection from
keydown to keyup.
previous commit broke some tests. The issue is that the search view
now avoid making requests if there is no action id. But this is an
assumption that tests use, so some slight adjustments have to be made.
Also, this is the moment to give properly the action id to the favorite
menu. Instead of bypassing its parent, it now receives the action id
from the search view.
Problem happens when the user from the website tries to load a translation,
it opens up a modal window without an action. But the modal has a (hidden)
searchview which tries to load custom filters corresponding to that
non-existing action.
Another problem at the same time was that the view manager could not
display the breadcrumbs for a non-existing breadcrumb.
The company_logo is cached and was not refreshed when switching between database, still showing the logo of the company of the previous database
Fixes#2738
This rev. 06104ba553
Added the dirty flag on the o2m field when the editor of the editable list was enabled (meaning that the editable list has been altered)) because the dirty flag was not set correctly by the one2many during the edition, at the time.
It looks like this is now the case
Besides, as now, we valid all the editable list of the form, wether or not the editable list was altered, we must not set the o2m as dirty anymore.
the buttons edit and create have been ungrouped recently. As a
side effect (of course), the bouncing effect in form view is broken.
This should hopefully fix the issue without introducing any other
problems :/
- stage model (project.task.type): add fields holding the eventual specific
legends for kanban states and star (priority) management
- project: task now have labels; you may use project to hold trainings
instead of tasks.
- project form: use label field on tasks statinfo to use the label
- project.task form: use kanban state customization using states_legend option;
- project.task kanban: use kanban column and kanban state cuztomization
using group_by_tooltip and states_legend options
- project_issue: issues now have labels, like tasks.
- issue: same kanban custo as for tasks
- update data and demo data
[IMP] web: statinfo widget now take an optional label_field option allowing
to have strings coming from another field present in the form view
search bar does not suggest date field format based on user's locale and always shows based on mmddyy using Date.parse, opw:615276
Note: starting in 9.0, datejs has been replaced by momentjs, so this
problem should be solved in a better way.
the filters menu can quickly grow if the user adds many conditions.
Once it grows out of the screen, the lower buttons can not be reached
anymore. This patch adds a vertical scrollbar to fix this issue. It
has to use some javascript to update its max-height property.
Kanban and form view kanban selection widgets can now be dependent of the
current stage of the record. The displayed legend can be taken directly
from the stage instead of the field selection values.
- added states_legend option on kanban selection widget for kanban and form
view: used to change the selection displayed value by a value coming from the
record given by group_by (kanban) / states_legend_field (form view). This allows
customizing the kanban selection widget depending on stages.
Improved the tooltip of kanban groups customization by improving the first
implementation of group_by_tooltip parameter in kanban view declaration.
This is done by adding some options and improving the first (still not
used) implementation:
- added group_by_tooltip option on field used to group on kanban view. Its
values is a collection of fields on the record used to group. The tooltip of
the group header will be the text formed from those fields values, allowing
custom tooltips for different kanban columns.
- now all data of the kanban columns are fetched in one call instead of doing
one call for each column. The various fields to read are collected by
introspecting the view definition.
Future commits will aim at using those features various addons, notably
in recruitment, project and crm.
Cedric Snauwaert