Bug 532 - clock doesn't resume after micropause
Status:
RESOLVED INVALID
Component:
Core :: Win32
Version:
unspecified
Hardware:
PC Windows
Importance:
P2 normal
Target Milestone:
---
Assignee:
Raymond Penners
URL:
Depends on:
Blocks:
Reported:
Jun 7 2006 21:34:01 UTC
by:
Thorin
Modified:
May 24 2017 12:59:32 UTC
CC List:
Stefan Monov
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Rob Caelers | Aug 18 2006 01:06:47 UTC | status | NEW | RESOLVED |
| resolution | INVALID | |||
| Stefan Monov | May 24 2017 12:03:45 UTC | cc | Stefan Monov |
Description
Thorin Jun 7 2006 21:34:01 UTC
Hello, I turned off the option 'stop clock during inactivity' (translated from Dutch; text might be different in English version). This works, except that after a micro pause is finished, the clock doesn't start counting down again unless you move the mouse or enter some keystrokes. I would expect that, after the micropause, the clock starts counting down again, even without activity. I use version 1.8.3
Comment 1
Rob Caelers Aug 18 2006 01:06:47 UTC
This is normal behaviour. When the 'Suspend timer when inactive' ('Stop de klok tijdens inactiviteit') is deselected, the timer starts when you become active. The timer keeps running until it is time to take a break. It even keeps running if you become inactive. When the break is over, the timer does not start counting again until you become active. This option is added for people who do a lot of reading. When reading, you are not actively using mouse/keyboard, but you are still using the computerComment 2
Stefan Monov May 24 2017 12:03:45 UTC
I have the same problem as the OP, except that: * I don't even have the option "Suspend timer when inactive" in my WorkRave * I have the problem with Rest Breaks rather than Micro-breaks (because I don't use Micro-breaks) I read in another thread that the option "Suspend timer when inactive" has been renamed with its opposite: "Reading mode". I do have "Reading mode" enabled, and I experience the behavior that Comment 1 says is normal. Let me explain why this behavior isn't desirable for me, though. I work on a Kubuntu laptop, but I have workrave running on another, Windows laptop, because on Kubuntu I have problems with the workrave panel applet. So I almost never have any mouse activity on the Windows laptop, and I have to remember to wiggle the mouse a bit after each break, to make it start counting. I realize the proper solution would be to fix the problems with the KDE applet, but if it's possible to just change the behavior described in Comment 1, I'd be happy too.
Comment 3
Stefan Monov May 24 2017 12:28:22 UTC
For reference, I just posted a report for the problem that stops me from using WorkRave on Kubuntu: https://issues.workrave.org/show_bug.cgi?id=1274
Comment 4
Kees-Jan Dijkzeul May 24 2017 12:38:04 UTC
(In reply to Stefan Monov from comment #2) Your post is leaving me in utter confusion. You are saying that you are running workrave on an entirely different machine, because you have problems with the KDE applet. Are you saying that these problems are preventing you from starting workrave on Kubuntu? Have you tried without using the applet? [...] > So I almost never have any mouse activity on the Windows laptop, and I have > to remember to wiggle the mouse a bit after each break, to make it start > counting. I understand. However. In a normal setup, during restbreaks the user is supposed to get up and go fetch coffee or something. If we implemented your suggestion, then, when the user returns from getting coffee, he will notice that his allotted working time is halfway over - just because he had an interesting chat at the coffee machine and things took a little longer. Users are not expected to sit behind their PCs, staring at the time ticking by in the break window. Frankly, neither should you, it is not healthy :-) As a result, yes, users have to inform workrave in some way that they are back and have resumed working. The way to currently do that is to wiggle the mouse and/or press some keys.
Comment 5
Stefan Monov May 24 2017 12:59:32 UTC
(In reply to Kees-Jan Dijkzeul from comment #4) Workrave would be pretty useless to me without the applet (or a systray icon), because I need a quick way to control it without having to alt+tab to the status window. Your rationale for WorkRave's behavior makes sense. I guess I'll have to wait for the report I linked to to be resolved.