The default window display all the events (aka 'fit'), in case of events spread over the year, the events are invisibles (too small to be readable)
Signed-off-by: adrien.didenot <adrien.didenot@horanet.com>
In Odoo calendar view, the attribute date_delay is an alternative to date_stop, to provides the duration of the event instead of its end date.
This commit integrate this attribute to the Timeline view, but contrary to the base Calendar view the Timeline view could use both arguments (date_stop and date_delay) simultaneously.
Signed-off-by: adrien.didenot <adrien.didenot@horanet.com>
* Update the vis.js framework to latest stable version (v4.20.1) to add new functionality and save almost
400ko of source code in odoo assets (the vis dev team has isolate the code for timeline widget from the
rest of their widgets)
* Add the possibility to display events with no duration (instantaneous) as the same time has regular events
* Add the possibility to choose between two scroll mode :
- zoom in time resolution (default)
or
- vertical scroll (web browser default behaviour)
Signed-off-by: adrien.didenot <adrien.didenot@horanet.com>
The problems found on Legacy Dialogs are the next:
1. The modal can't be dragged
2. The button for extending and reduce the modal is doing nothing
3. The x for close the modal is showed twice
You can test it with dialogs showed on Vault module
[IMP] web_dialog_size: Migration to 16.0
[REM] Remove duplicate configuration readme file
[FIX] Make it work for normal dialogs also
[FIX] SelectCreateDialog
precommit
It is important to let users decide their default dialog size. Some have ultrawide monitors and this module does more harm than benefit.
Here I add such task to roadmap, to avoid forgetting about it.
@Tecnativa
Checking result of rpc call, `dialog_maximize`, will end to be always `true` as the method will return a json: `{'dialog_maximize': false }`. So i changed the test to test the value of json key `dialog_maximize`
This addon had 2 problems after migrating to v11:
1. One call to backend's `ir.config_parameter.get_param` was done for
each instantiated dialog, while the setting served for the whole
session equally.
2. That model is now readable only by admin users, so non-admins
couldn't use the default at all.
Fixed now.
