Odoo/addons/timer/models/timer_mixin.py, branch 14.0 The current checkout of upstream Odoo [FIX] timer: remove leftover file 2020-07-29T15:40:21+00:00 Christophe Simonis chs@odoo.com 2020-07-29T12:23:50+00:00 92c2a54505db453d2a1b08ed324e173dff05c021 Oversight of d6a23144d5c5b85c2a02097bcbb3e006a9c2c52a closes odoo/odoo#55165 X-original-commit: a8d450f2339d1e788d50455e3c5ad009155b99ee Signed-off-by: Christophe Simonis <chs@odoo.com> 
Oversight of d6a23144d5c5b85c2a02097bcbb3e006a9c2c52a

closes odoo/odoo#55165

X-original-commit: a8d450f2339d1e788d50455e3c5ad009155b99ee
Signed-off-by: Christophe Simonis <chs@odoo.com>
[FIX] timer, hr_timesheet: Fix _compute_display_timer_buttons 2020-06-11T14:00:06+00:00 Thibault Francois tfr@openerp.com 2020-06-11T11:32:58+00:00 ab48798229d4c756ab31fd0f1fa5518ef8e63037 mixin method should not return in the middle of the loop Use the value updated on the record instead super() is called with self at every iteration which is not very efficient and can be wrong Solution call super for each specific record and only when needed write is not a good practice in compute method closes odoo/odoo#52858 X-original-commit: 7e19ed98d18305370b5c14edd3d310cfea5df714 Related: odoo/enterprise#11100 Signed-off-by: Yannick Tivisse (yti) <yti@odoo.com> 
mixin method should not return in the middle of the loop
Use the value updated on the record instead

super() is called with self at every iteration
which is not very efficient and can be wrong

Solution call super for each specific record
and only when needed

write is not a good practice in compute method

closes odoo/odoo#52858

X-original-commit: 7e19ed98d18305370b5c14edd3d310cfea5df714
Related: odoo/enterprise#11100
Signed-off-by: Yannick Tivisse (yti) <yti@odoo.com>
[ADD] timer: New mixin to record time on models 2020-02-05T15:44:37+00:00 Okan SUMER (osu) osu@odoo.com 2020-02-05T15:15:29+00:00 e2b749fb7a441b4337c40cc856459e2e5f95b597 Purpose ======= The timer mechanism is already existing on timesheet. We would like to introduce it on helpdesk.ticket too, and probably on other models afterward. On the other hand, only one timer can be launched on a single timesheet currently, shared amongst the different users. This commit introduced a new mixin on which - Each user can launch a timer on each record of the models inheriting the mixin. - Launching a new timer on a record pauses the timer of the user that could be already running. - The mixin brings methods to start/stop/pause/resume the timer, that could be overridden to implement a specific behavior for the related model, for example create a timesheet entry. TaskID: 2149450 
Purpose
=======

The timer mechanism is already existing on timesheet.

We would like to introduce it on helpdesk.ticket too, and
probably on other models afterward.

On the other hand, only one timer can be launched on a single
timesheet currently, shared amongst the different users.

This commit introduced a new mixin on which
- Each user can launch a timer on each record of the models
  inheriting the mixin.
- Launching a new timer on a record pauses the timer of the
  user that could be already running.
- The mixin brings methods to start/stop/pause/resume the
  timer, that could be overridden to implement a specific
  behavior for the related model, for example create a
  timesheet entry.

TaskID: 2149450