Only one timer at a time should be active.

We should only allow a single timer to be running at any giv

Wed, 07 Aug 2013 17:25:22 +0000

We should only allow a single timer to be running at any given time. So, starting one timer should pause all other active timers.

> We should only allow a single timer to be running at any g

Wed, 07 Aug 2013 17:34:21 +0000

> 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.

I guess I don't see why we would be charging time to two dif

Wed, 07 Aug 2013 18:01:21 +0000

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.

Tue, 26 Nov 2013 19:53:54 +0000

Changes have been made in Git (master): commit 5064b9624dd98bacc38587679cff7df92db7567a Author: Michael J Rubinsky 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

Only one timer at a time should be active.

We should only allow a single timer to be running at any giv

> We should only allow a single timer to be running at any g

I guess I don't see why we would be charging time to two dif

See also Bug: 6550

Changes have been made in Git (master): commit 5064b9624dd9