Bug 664 - 'Lock' function on rest break stops timer
Status:
RESOLVED FIXED
Component:
Build-Env
Version:
1.8.4
Hardware:
PC Windows XP
Importance:
P4 normal
Target Milestone:
---
Assignee:
Rob Caelers
URL:
Depends on:
Blocks:
Reported:
Aug 15 2007 02:23:38 UTC
by:
gavin
Modified:
Sep 19 2007 22:43:28 UTC
CC List:
Ray Satiro
WhoWhenWhatRemovedAdded
Ray SatiroAug 16 2007 05:05:54 UTCccRay Satiro
Rob CaelersAug 27 2007 14:04:11 UTCpriorityP2P4
Ray SatiroSep 19 2007 22:43:28 UTCstatusNEWRESOLVED
resolutionFIXED
Description
gavin  Aug 15 2007 02:23:38 UTC
There is a lock function on the rest break timer.  

If I select this and lock my PC whilst the exercises are showing on screen, the timer continues to run and the break times out normally.

If I select this after the exercises have been shown, i.e. just the break length countdown timer is displayed, the timer stops at the time it shows when I hit the button.  No matter how long I am away from my screen for, when I come back and unlock my screen the timer is still sitting at the same time.  The only way to get out of this is to skip or postpone the break.
Comment 1
Ray Satiro  Aug 16 2007 05:05:33 UTC
Is 'Suspend timer when inactive' disabled?
Comment 2
Ray Satiro  Aug 16 2007 05:05:54 UTC
Is 'Suspend timer when inactive' disabled?
Comment 3
gavin  Aug 16 2007 05:51:02 UTC
(In reply to comment #2)
> Is 'Suspend timer when inactive' disabled?

Yes, it is, i.e. tick box is unchecked.
Comment 4
Ray Satiro  Aug 17 2007 06:22:30 UTC
The bug you are reporting is probably related to a timer freeze issue that occurs when 'suspend timer when inactive' is disabled. The fix will be in the next release of Workrave.

As a temporary fix, enable 'suspend timer when inactive' until the next release. If you can't wait for the next release, you can download a recent nightly build. Nightly builds might have stability issues of their own.

http://workrave.org/download/snapshots/20070812/workrave-win32-20070812-installer.exe
Comment 5
Rob Caelers  Aug 27 2007 12:46:29 UTC
*** Bug 663 has been marked as a duplicate of this bug. ***