Bug 926 - Reading mode reversed?
Status:
RESOLVED INVALID
Component:
Core :: Win32
Version:
1.9.2
Hardware:
PC Windows XP
Importance:
P5 minor
Target Milestone:
---
Assignee:
Raymond Penners
URL:
Depends on:
Blocks:
Reported:
Sep 23 2010 07:23:38 UTC
by:
John
Modified:
Nov 19 2010 19:29:06 UTC
CC List:
Kees-Jan Dijkzeul
Sabine
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Kees-Jan Dijkzeul | Sep 23 2010 08:13:00 UTC | cc | Kees-Jan Dijkzeul | |
| John | Sep 23 2010 20:54:17 UTC | status | NEW | RESOLVED |
| resolution | INVALID | |||
| Sabine | Nov 19 2010 19:29:06 UTC | cc | Sabine |
Description
John Sep 23 2010 07:23:38 UTC
Thanks for the addition of reading mode! I wonder if the activation is reversed? It operates when 'Reading mode' is *unchecked* and is deactivated when 'Reading mode' is *checked* - not what I expected! And thanks hugely for a superb utility! John
Comment 1
Kees-Jan Dijkzeul Sep 23 2010 08:13:00 UTC
(In reply to comment #0) > Thanks for the addition of reading mode! I wonder if the activation is > reversed? It operates when 'Reading mode' is *unchecked* and is deactivated > when 'Reading mode' is *checked* - not what I expected! I just checked. For me, reading mode works as expected. Just to be sure: How do you expect reading mode to work? ;-)
Comment 2
John Sep 23 2010 11:20:11 UTC
Thanks for checking, Kees-Jan. When 'Reading mode' is checked, I expect that when I'm simply reading, with no mouse or kbd input, that the timer will pause after say, 2 mins, and resume when input in next detected ... and so on ... This now seems to happen when 'Reading mode' is *unchecked* and not when 'Reading mode' is checked. I'll do some more precise tests tomorrow and post actual timings for each state. And do tell me how it's intended to work ;-)
Comment 3
Kees-Jan Dijkzeul Sep 23 2010 12:50:00 UTC
(In reply to comment #2) I think you have your expectations reversed. In "normal mode", timers will keep running as long as you are using keyboard/mouse, and will stop running if you stop using them (within 5 seconds or so). In "reading mode", timers will start running when you use keyboard/mouse, and then keep running until the next break, _even_if_ you stop using keyboard/mouse (i.e. if you are just reading from the screen). Reading mode is intended to warn you to take a break, even when you are not using the keyboard/mouse, so timers will never stop running (well, at least until the next restbreak, iirc). Does this help?
Comment 4
John Sep 23 2010 20:54:17 UTC
(In reply to comment #3) > (In reply to comment #2) > ... Does this help? Yes, this does help, thanks, Kees-Jan. My expectations were indeed reversed. I was expecting 'Reading mode' to be the newly implemented mode, but it turns out that it's *normal* mode that has the new behaviour, with the timers stopping with inactivity - unlike the *old* normal mode, where they'd just keep on running. So the new normal mode gives me exactly what I want - that the timers should stop if I move off the computer, to answer the phone, go to check out something with a colleague, ... Thanks! Clearly not a bug, then! John
Comment 5
Sabine Nov 19 2010 19:29:06 UTC
In "normal mode", timers will keep running as long as you are using keyboard/mouse, and will stop running if you stop using them (within 5 seconds or so). Oh please please please make it so we can customize the idle time in the next version? So that the "5 seconds or so" you mentioned can be customizable? It would be perfect!