· Workrave

Bug 87 - wr considers me active during a wp micropause

Status:

VERIFIED FIXED

Component:

Core

Version:

unspecified

Hardware:

PC Windows NT

Importance:

P1 blocker

Target Milestone:

---

Assignee:

Raymond Penners

URL:

Depends on:

Blocks:

Reported:

Sep 17 2002 21:17:27 UTC

by:

Kees-Jan Dijkzeul

Modified:

Sep 23 2002 02:02:46 UTC

Id	Who	When	Size	Type
6	log of this problem
6	Kees-Jan Dijkzeul	Sep 20 2002 02:49:01 UTC	22584	application/octet-stream
7	Logged while taking a wp micropause
7	Kees-Jan Dijkzeul	Sep 20 2002 02:56:21 UTC	6279	text/plain

Who	When	What	Removed	Added
Kees-Jan Dijkzeul	Sep 17 2002 22:10:17 UTC	blocks		52
Kees-Jan Dijkzeul	Sep 19 2002 01:17:52 UTC	priority	P3	P1
Kees-Jan Dijkzeul	Sep 19 2002 01:17:52 UTC	severity	normal	blocker
Raymond Penners	Sep 20 2002 09:53:15 UTC	assigned_to	Rob Caelers	Raymond Penners
Raymond Penners	Sep 20 2002 09:54:03 UTC	status	NEW	RESOLVED
Raymond Penners	Sep 20 2002 09:54:03 UTC	resolution		FIXED
Kees-Jan Dijkzeul	Sep 23 2002 02:02:46 UTC	status	RESOLVED	VERIFIED

Description

Kees-Jan Dijkzeul Sep 17 2002 21:17:27 UTC

When wp tells me to micropause, wr still considers me active. wr only switches 
to "idle" five seconds after the wp micropause window has gone.

Comment 1

Kees-Jan Dijkzeul Sep 17 2002 21:21:59 UTC

I just had a wp restbreak without wr considering me active. However, the 
disappearing of the wp restbreak window was considered activity. Therefore I 
did not complete my wr natural restbreak. (I would expect this to at least be 
within the noise threshold)

Comment 2

Kees-Jan Dijkzeul Sep 17 2002 22:10:17 UTC

Not only wp is to blame for this behaviour. I now have wp micropauses and 
restbreaks disabled.

Just a minute ago, my screensaver activated (set at 10 minutes, equal to my 
rest break duration), with by restbreak window showing about 7 minutes of 
remaining time.

Apparently wr generates some internal activity??

Comment 3

Kees-Jan Dijkzeul Sep 19 2002 01:17:52 UTC

This is highly annoying. I can't even complete a restbreak any more

Comment 4

Kees-Jan Dijkzeul Sep 19 2002 03:46:31 UTC

Hypothesis:
Scrolling text in a cygwin window causes events to be generated, even when idle

Comment 5

Kees-Jan Dijkzeul Sep 20 2002 02:49:01 UTC

Created attachment 6
log of this problem

Comment 6

Kees-Jan Dijkzeul Sep 20 2002 02:50:46 UTC

Gotcha

wr just prompted a micropause. I took it. I was waiting for wp to detect a 
natural break. Then, the logging goes

>>> GUI::timer_action daily_limit 0
<<< GUI::timer_action
>>> GUI::timer_action micro_pause 0
<<< GUI::timer_action
>>> GUI::timer_action rest_break 0
<<< GUI::timer_action
>>> Control::process_timers
    Control::process_timers run
>>> GUI::timer_action daily_limit 0
<<< GUI::timer_action
>>> GUI::timer_action micro_pause 0
<<< GUI::timer_action
>>> GUI::timer_action rest_break 0
<<< GUI::timer_action
>>> Win32InputMonitor::mouse_hook 512, (616, 707, 30710)
>>> Control::process_timers
    Control::process_timers run
>>> GUI::timer_action daily_limit 0
<<< GUI::timer_action
>>> GUI::timer_action micro_pause 0
<<< GUI::timer_action
>>> GUI::timer_action rest_break 0
<<< GUI::timer_action
>>> Control::process_timers
    Control::process_timers run
>>> GUI::timer_action daily_limit 0
<<< GUI::timer_action
>>> GUI::timer_action micro_pause 0
<<< GUI::timer_action
>>> GUI::timer_action rest_break 0
<<< GUI::timer_action
>>> Control::process_timers
    Control::process_timers run
>>> GUI::timer_action daily_limit 0
<<< GUI::timer_action
>>> GUI::timer_action micro_pause 0
<<< GUI::timer_action
>>> GUI::timer_action rest_break 0
<<< GUI::timer_action
>>> Win32InputMonitor::mouse_hook 512, (616, 707, 30710)
>>> Win32InputMonitor::mouse_hook 512, (616, 707, 30710)
>>> Control::process_timers
    Control::process_timers run
>>> Timer::compute_next_limit_time micro_pause
<<< Timer::compute_next_limit_time1032515264
>>> Timer::compute_next_limit_time rest_break
<<< Timer::compute_next_limit_time1032515914
>>> GUI::timer_action daily_limit 0
<<< GUI::timer_action
>>> GUI::timer_action micro_pause 2
<<< GUI::timer_action
>>> GUI::timer_action rest_break 2
<<< GUI::timer_action
>>> Win32InputMonitor::mouse_hook 512, (616, 707, 30710)
>>> Win32InputMonitor::mouse_hook 512, (616, 707, 30710)
>>> Win32InputMonitor::mouse_hook 512, (616, 707, 30710)
>>> Win32InputMonitor::mouse_hook 512, (616, 707, 30710)
>>> Win32InputMonitor::mouse_hook 512, (616, 707, 30710)
>>> Win32InputMonitor::mouse_hook 512, (616, 707, 30710)
>>> Win32InputMonitor::mouse_hook 512, (616, 707, 30710)
>>> Win32InputMonitor::mouse_hook 512, (616, 707, 30710)
>>> Win32InputMonitor::mouse_hook 512, (616, 707, 30710)
>>> Win32InputMonitor::mouse_hook 512, (616, 707, 30710)
>>> Control::process_timers
    Control::process_timers run
>>> Timer::compute_next_limit_time daily_limit
<<< Timer::compute_next_limit_time1032528912
>>> GUI::timer_action daily_limit 2
<<< GUI::timer_action
>>> GUI::timer_action micro_pause 0
<<< GUI::timer_action
>>> GUI::timer_action rest_break 0
<<< GUI::timer_action
>>> Control::process_timers
    Control::process_timers run
>>> GUI::timer_action daily_limit 0
<<< GUI::timer_action
>>> GUI::timer_action micro_pause 0
<<< GUI::timer_action
>>> GUI::timer_action rest_break 0
<<< GUI::timer_action
>>> Control::process_timers
    Control::process_timers run

This raises two questions
- What causes these events (I can recall nothing exciting happening)
- Why are these events considered, since they are mouse events occuring at the 
same place.

Comment 7

Kees-Jan Dijkzeul Sep 20 2002 02:56:21 UTC

Created attachment 7
Logged while taking a wp micropause

Attachments

history