Tickets :: [#12543] Only one timer at a time should be active.

6.0.0-beta1

8/26/25

Summary	Only one timer at a time should be active.
Queue	Hermes
Queue Version	Git master
Type	Enhancement
State	Resolved
Priority	1. Low
Owners	mrubinsk (at) horde (dot) org
Requester	mrubinsk (at) horde (dot) org
Created	08/07/2013 (4402 days ago)
Due
Updated	11/26/2013 (4291 days ago)
Assigned	08/07/2013 (4402 days ago)
Resolved	11/26/2013 (4291 days ago)
Milestone
Patch	No

11/26/2013 07:56:10 PM	Michael Rubinsky	Type ⇒ Enhancement State ⇒ Resolved Priority ⇒ 1. Low

11/26/2013 07:53:54 PM	Git Commit	Comment #5	Reply to this comment
Changes have been made in Git (master): commit 5064b9624dd98bacc38587679cff7df92db7567a Author: Michael J Rubinsky <mrubinsk@horde.org> Date: Tue Nov 26 14:53:13 2013 -0500 Implement exclusive/non-exclusive timers. ~~Request: 12543~~ hermes/js/hermes.js \| 14 +++++- hermes/lib/Ajax/Application/Handler.php \| 21 +++------ hermes/lib/Hermes.php \| 70 ++++++++++++++++++++++------- hermes/templates/dynamic/timer.inc \| 7 +++ hermes/themes/default/dynamic/screen.css \| 9 +++- 5 files changed, 87 insertions(+), 34 deletions(-) http://git.horde.org/horde-git/-/commit/5064b9624dd98bacc38587679cff7df92db7567a

08/07/2013 06:03:55 PM	Michael Rubinsky	Comment #4	Reply to this comment
See also ~~Bug: 6550~~

08/07/2013 06:01:21 PM	Michael Rubinsky	Comment #3	Reply to this comment
I guess I don't see why we would be charging time to two different cost objects/clients/whatever at once. But then again, I guess I'm assuming the timers are only used for timing billable events. I had a timer running for another reason, but failed to stop it when I started a new one. While I can figure out what time to substract from the first one to make it "right" again, it can lead to overcharging a cost object if the user doesn't notice it didn't stop the other timers. I guess an option when creating the timer to make it "exclusive" would work here as well.

08/07/2013 05:34:21 PM	Jan Schneider	Comment #2	Reply to this comment
We should only allow a single timer to be running at any given time. So, starting one timer should pause all other active timers. Why? It might make perfect sense to have several timers running. At least this should be optional when starting a new timer.

08/07/2013 05:25:22 PM	Michael Rubinsky	Comment #1 Priority ⇒ 1. Low Type ⇒ Bug Summary ⇒ Only one timer at a time should be active. Queue ⇒ Hermes Assigned to Michael Rubinsky Milestone ⇒ Patch ⇒ No State ⇒ Assigned	Reply to this comment
We should only allow a single timer to be running at any given time. So, starting one timer should pause all other active timers.