Bug 792 - micro-brake count down error
Status:
RESOLVED INVALID
Component:
GUI
Version:
1.9.0
Hardware:
PC All
Importance:
P4 normal
Target Milestone:
---
Assignee:
Rob Caelers
URL:
Depends on:
Blocks:
Reported:
Oct 24 2008 11:40:21 UTC
by:
Rushikesh
Modified:
Nov 6 2008 21:48:35 UTC
CC List:
Kees-Jan Dijkzeul
WhoWhenWhatRemovedAdded
Kees-Jan DijkzeulOct 25 2008 20:50:53 UTCccKees-Jan Dijkzeul
Rob CaelersNov 6 2008 21:48:35 UTCstatusNEWRESOLVED
resolutionINVALID
Description
Rushikesh  Oct 24 2008 11:40:21 UTC
Steps to reproduce:

1. Run the Workrave in Windows / Fedora 7
2. Change the micro-brake settings as follows:
   a. Time between breaks : 5 minutes
   b. Break duration : 15 seconds
   c. Postpone time : 2.30 minutes
   d. Maximum number of prompts : 15

3. After 5 minutes, micro-brake appears saying:
   
   Time for a micro-break?
   Disappearing in 30 seconds

   And then the "Disappearing in 30 seconds" count downs (I assume it should start counting down from 15 seconds

4. After 5-6 seconds, another dialog box appears, where the counting start from 10 or 9 seconds.
Comment 1
Kees-Jan Dijkzeul  Oct 25 2008 20:50:53 UTC
This is normal behavior.

The "Disappearing in 30 seconds" window (we call it a prelude) warns you that it is time to take a break, and asks you to stop working. If you like, you can use those 30 seconds to finish a sentence or anything.

After you stop working, Workrave takes about 4-5 seconds to detect that you actually stopped. If you stop working immediately when the prelude window appears, then those seconds are subtracted from your break time, hence your break time seems to cunt down from 10 or 9 or so, but you should notice that the progress bar is already one third filled, indicating the other 5 seconds of your break.

If you do not stop working when the prelude appears, but only a little later (say after you finish your sentence), then the 5 seconds workrave needs to detect that you stopped are not subtracted, hence your break will count down from 15.
Comment 2
Rob Caelers  Nov 6 2008 21:48:35 UTC
This behavior is intentional as Kees-Jan mentions. Closing bug.