Bug 1062 - User activity tracking stops, when working on a second monitor which is ABOVE the default display.
Status:
RESOLVED FIXED
Component:
Core :: Win32
Version:
1.9.4
Hardware:
All All
Importance:
P5 normal
Target Milestone:
---
Assignee:
Raymond Penners
URL:
Depends on:
Blocks:
Reported:
Jan 22 2012 00:01:07 UTC
by:
Peter
Modified:
Aug 25 2012 15:41:13 UTC
CC List:
Kevin
Rob Caelers
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Kevin | Jan 29 2012 19:53:45 UTC | cc | Kevin | |
| Rob Caelers | Feb 11 2012 14:07:59 UTC | cc | Rob Caelers | |
| Rob Caelers | Aug 25 2012 15:41:13 UTC | status | NEW | RESOLVED |
| resolution | FIXED |
Description
Peter Jan 22 2012 00:01:07 UTC
I use a second monitor ABOVE my notebook screen. When I work there (keyboard or mouse), workrave treats this a no activity. Even if I type and move the mouse. It seems to be connected to the position of the focused window - and not the mouse position: When the focused window is on the primary screen and I move the mouse on the second screen, the countdown continues. Windows 7.
Comment 1
Peter Jan 22 2012 00:02:19 UTC
PS: When I have my notebook at work, I use the second display RIGHT of the default screen - and this works well.
Comment 2
Kevin Jan 29 2012 19:53:45 UTC
I have a similar issue - I have a second monitor which is to the LEFT of the 'primary' monitor. WorkRave fails to 'lock' this monitor during a break. I believe the problem MAY be in the routine GUI::init_multihead_desktop(). I know from my own Windows desktop programming that my 'left' monitor has a X location which is NEGATIVE. So this line may fail to expand the "screen" size correctly: int w = heads[i].geometry.get_x() + heads[i].geometry.get_width(); In the case of Peter's report, his monitor ABOVE his primary display probably has a Y location which is NEGATIVE. I am assuming that the GDK::Screen class returns the same geometry as the Windows GUI methods.
Comment 3
Rob Caelers Feb 11 2012 14:07:59 UTC
Peter, could you please check if the following version fixes the problem: http://snapshots.workrave.org/20120211/workrave-win32-v1_9_904-17-g12247837ff-dirty-20120211-installer.exe Kevin, as far as I know, Gdk always returns positive values for the monitor location. You wrote "WorkRave fails to 'lock' this monitor during a break.". So workrave does not block keyboard/mouse on this monitor during breaks? Do you still get a break window on this monitor?
Comment 4
Kevin Feb 11 2012 19:03:18 UTC
> Do you still get a break window on this monitor? The "rest break" dialog does appear on the "left" monitor. The monitor is not "locked" in the sense that all windows are hidden as on the primary monitor. > So workrave does not block keyboard/mouse on this monitor during breaks? Effectively no. I am unable to interact with Thunderbird, but I *can* set focus to a notepad window and type it in during a break.
Comment 5
Kevin Feb 11 2012 19:08:26 UTC
> http://snapshots.workrave.org/20120211/workrave-win32-v1_9_904-17-g12247837ff-dirty-20120211-installer.exe This version is much improved re: locking mouse/keyboard on my "left" monitor. I cannot type into Notepad, nor grab a gadget. I can still click on Notepad to get input focus but that's pretty much it. Looking good! Kevin
Comment 6
Rob Caelers Aug 25 2012 15:41:13 UTC
Thanks for testing (and sorry for the huge delay...). I'm afraid the issue that you can give Notepad focus is hard to fix.