Bug 25 - Timer keeps running when inactive
Status:
VERIFIED FIXED
Component:
GUI :: gtkmm
Version:
unspecified
Hardware:
PC Windows NT
Importance:
P1 critical
Target Milestone:
---
Assignee:
Raymond Penners
URL:
Depends on:
Blocks:
Reported:
Sep 2 2002 21:36:05 UTC
by:
Kees-Jan Dijkzeul
Modified:
Oct 22 2002 01:54:46 UTC
| Id | Who | When | Size | Type |
|---|---|---|---|---|
| 3 | wr log file | |||
| Kees-Jan Dijkzeul | Sep 6 2002 21:37:14 UTC | 152758 | application/octet-stream | |
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Kees-Jan Dijkzeul | Sep 3 2002 21:55:41 UTC | severity | normal | critical |
| priority | P3 | P1 | ||
| Raymond Penners | Sep 6 2002 21:48:24 UTC | assigned_to | Rob Caelers | Raymond Penners |
| Raymond Penners | Sep 6 2002 21:57:46 UTC | status | NEW | RESOLVED |
| resolution | FIXED | |||
| Kees-Jan Dijkzeul | Sep 9 2002 20:54:43 UTC | status | RESOLVED | VERIFIED |
Description
Kees-Jan Dijkzeul Sep 2 2002 21:36:05 UTC
Soms, als ik een micropauze zou moeten nemen, blijft de teller doorlopen, terwijl ik niks doe. Dit gebeurt o.a. wanneer workpace (ja, ik gebruik allebei) ook vindt dat ik moet pauzeren. wp en wr proberen allebei een window op de voorgrond te krijgen. Dat geeft een knipperend effect... Wordt het 'loose focus' event gezien als activiteit? Is het 'loose focus' event een trigger, om het window weer op de voorgrond te zetten??
Comment 1
Kees-Jan Dijkzeul Sep 3 2002 21:55:41 UTC
Gebeurt ook als workpace gewoon niks doet. Erg irritant. De pauzes duren zo langer dan je geconfigureerd hebt.
Comment 2
Raymond Penners Sep 5 2002 21:58:22 UTC
I cannot reproduce this.
Could you please check the mouse coordinates that are logged to the console and
tell me if the coordinates change?
0x138539000 | Win32InputMonitor::mouse_hook 512, (278, 447)
0x138539000 | Win32InputMonitor::mouse_hook 512, (283, 457)
^^^^^^^^^
coordinates
Btw, you'll need the latest and greatest harpoon.dll and workrave.
Comment 3
Kees-Jan Dijkzeul Sep 6 2002 21:37:14 UTC
Created attachment 3
wr log file
In this particular scenario both the wp and wr restbreak windows are competing
to be on top. My mouse is in both. The logging (see attachment) goes like:
>>> 0x129d48000 | Win32InputMonitor::mouse_hook 512, (568, 434)
>>> 0x129d48000 | Win32InputMonitor::mouse_hook 512, (568, 434)
>>> 0x129d48000 | Win32InputMonitor::mouse_hook 512, (568, 434)
0x12615c000 | Control::run 603 0
0x12615c000 | Control::run 0 20
0x12615c000 | Control::run 549 600
>>> 0x126540000 | GUI::inter_thread_call
>>> 0x126540000 | BreakControl::heartbeat
0x126540000 | BreakControl::heartbeat state = 1 4 548
0x126540000 | BreakControl::heartbeat stage = 3
0x126540000 | BreakControl::heartbeat idle = 549
0x126540000 | BreakControl::heartbeat tstate = 2
<<< 0x126540000 | BreakControl::heartbeat
<<< 0x126540000 | GUI::inter_thread_call
>>> 0x129d48000 | Win32InputMonitor::mouse_hook 512, (568, 434)
>>> 0x129d48000 | Win32InputMonitor::mouse_hook 512, (568, 434)
>>> 0x129d48000 | Win32InputMonitor::mouse_hook 512, (568, 434)
0x12615c000 | Control::run 604 0
0x12615c000 | Control::run 0 20
0x12615c000 | Control::run 550 600
>>> 0x126540000 | GUI::inter_thread_call
>>> 0x126540000 | BreakControl::heartbeat
0x126540000 | BreakControl::heartbeat state = 1 4 549
0x126540000 | BreakControl::heartbeat stage = 3
0x126540000 | BreakControl::heartbeat idle = 550
0x126540000 | BreakControl::heartbeat tstate = 2
<<< 0x126540000 | BreakControl::heartbeat
<<< 0x126540000 | GUI::inter_thread_call
>>> 0x129d48000 | Win32InputMonitor::mouse_hook 512, (568, 434)
>>> 0x129d48000 | Win32InputMonitor::mouse_hook 512, (568, 434)
>>> 0x129d48000 | Win32InputMonitor::mouse_hook 512, (568, 434)
0x12615c000 | Control::run 605 0
0x12615c000 | Control::run 0 20
0x12615c000 | Control::run 551 600
>>> 0x126540000 | GUI::inter_thread_callComment 4
Raymond Penners Sep 6 2002 21:48:24 UTC
If you look through the log, you'll notice that the same mouse coordinates are being logged. I'll modify the activity monitor to ignore such events, but first some modifications are necessary for it to receive coordinates at all...
Comment 5
Raymond Penners Sep 6 2002 21:57:46 UTC
It's in...