Bug 818 - Micro break count down not continuing after completion
Status:
RESOLVED DUPLICATE
Component:
Core :: Win32
Version:
1.9.0
Hardware:
PC Windows XP
Importance:
P5 normal
Target Milestone:
---
Assignee:
Ray Satiro
URL:
Depends on:
Blocks:
Reported:
Feb 26 2009 23:20:02 UTC
by:
an**@gm**.com
Modified:
Jul 15 2009 21:41:56 UTC
CC List:
Gus Gustafson
Ray Satiro
Rob Caelers
WhoWhenWhatRemovedAdded
Ray SatiroMar 1 2009 22:06:25 UTCstatusNEWASSIGNED
severitymajornormal
assigned_toRaymond PennersRay Satiro
ccRay Satiro
Gus GustafsonJul 9 2009 17:54:36 UTCccGus Gustafson
Rob CaelersJul 15 2009 21:41:56 UTCresolutionDUPLICATE
ccRob Caelers
statusASSIGNEDRESOLVED
Description
an**@gm**.com  Feb 26 2009 23:20:02 UTC
Hi, 

What a great little tool! 

One thing I noticed though; is that if you do not suspend the timer when inactive - when the micro break timer finishes after the break duration, it only continues the count down after mouse or keyboard input. 
This is annoying as I use Workrave when reading docs, and use the micro break prompt to look away from the screen / move etc. 
This is also noticed on Vista.  

Thanks for the good work =]
Comment 1
Ray Satiro  Mar 1 2009 22:06:25 UTC
Workrave requires input to start a timer. How often are your micro-breaks? Can you give steps to reproduce your experience?

Thanks,

Ray
Comment 2
Gus Gustafson  Jul 9 2009 17:54:36 UTC
"Workrave requires input to start a timer."

This is not good. not everyone uses workrave just for wrist rsi (i use for eye and walking breaks while looking at the screen and writing in paper notebook, not typing), so it should not require any input. I use a mac at work, which has the program called "Time Out". This one does not require any input to restart timer. Workrave should not either.
Comment 3
Gus Gustafson  Jul 9 2009 18:03:21 UTC
why require input, isn't that what the "suspend timer when inactive" option is for?
Comment 4
Rob Caelers  Jul 15 2009 21:41:56 UTC
It seems 847 is a duplicate of this bug. I added a proposed solution to 847. So I'm marking this bug as duplicate.

*** This bug has been marked as a duplicate of bug 847 ***