Bug 573 - Workrave does not always display during breaks
Status:
RESOLVED DUPLICATE
Component:
Core :: Win32
Version:
1.8.3
Hardware:
PC Windows Vista
Importance:
P4 normal
Target Milestone:
---
Assignee:
Ray Satiro
URL:
Depends on:
Blocks:
Reported:
Dec 8 2006 18:48:36 UTC
by:
Scott McDermott
Modified:
Jun 24 2008 05:53:45 UTC
WhoWhenWhatRemovedAdded
Rob CaelersAug 27 2007 14:04:00 UTCpriorityP2P4
Ray SatiroSep 30 2007 02:12:13 UTCassigned_toRaymond PennersRay Satiro
Ray SatiroJun 24 2008 05:53:45 UTCstatusNEWRESOLVED
resolutionDUPLICATE
Description
Scott McDermott  Dec 8 2006 18:48:36 UTC
Workrave often does not display during breaks. I will hear the chime to let me know a break has started, but the window is not visible. It's very disconcerting if you do not hear the chime for some reason and your computer stops responding. It's also a drag if the timing for the break is poor, since you have no way to postpone it...
Comment 1
Rob Caelers  Feb 13 2007 00:00:06 UTC
Could it be a duplicate of bug #587 ?

Vista is not officially supported yet...
Comment 2
Scott McDermott  Feb 13 2007 03:02:33 UTC
(In reply to comment #1)
> Could it be a duplicate of bug #587 ?

As best I can tell, yes.
Comment 3
Ray Satiro  Sep 30 2007 02:12:13 UTC
The break warning not coming to the front should be fixed in 1.8.5
The break window comes to the front in all my recent testing.

Please try 1.8.5
If the break window still doesn't come to the front, there is an undocumented
feature you can use to force the focus on it, "popping" it to the top
(hopefully).

Also, you can CTRL+ALT+DEL to start taskmgr and end task on Workrave 1.8.5 if
it locks up on you.

It's important that you let us know if you still have this problem with 1.8.5

--

Please try Workrave 1.8.5, and tell us if you experience the same problem.

http://superb-west.dl.sourceforge.net/sourceforge/workrave/workrave-win32-1.8.5-installer.exe
1b732b368fae346712f55c013fd86e93 *workrave-win32-1.8.5-installer.exe

Thanks,

Ray
Comment 4
Ray Satiro  Jun 24 2008 05:53:45 UTC

*** This bug has been marked as a duplicate of bug 587 ***