After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 640100 - Dead space in dual monitor setup makes message tray difficult to open
Dead space in dual monitor setup makes message tray difficult to open
Status: RESOLVED NOTGNOME
Product: gnome-shell
Classification: Core
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
: 639973 645599 (view as bug list)
Depends on:
Blocks: 645023
 
 
Reported: 2011-01-20 19:57 UTC by Tanuva
Modified: 2011-03-23 17:49 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
The monitor layout (2.82 KB, image/png)
2011-01-20 19:57 UTC, Tanuva 		Details

Description Tanuva 2011-01-20 19:57:03 UTC 
Created attachment 178879 [details]
The monitor layout

I have two monitors with different heights aligned at the top edge. Therefore, there's some dead space under the "Laptop" monitor which is the primary one.

If I (carefully) try to open the message tray just by touching the lowermost >visible< pixel row, it disappears immediately when moving the mouse back upward to click in the tray.
If I move the mouse into the dead/invisible space and then raise it again, the tray stays open upon reaching the lowermost visible row and I can click onto it.

At least that's my interpretation of whats happening...
Comment 1 Dan Winship 2011-01-20 20:11:15 UTC 
so, if we're not going to get any sort of "mouse barriers" in the 3.0 timeframe, one thing we could do for this layout would be to notice that there's dead space under the tray and make its "hot spot" extend down into the dead space; you'd still end up overshooting the pointer into the dead space, but at least the tray would stay visible while you moved the mouse back into visible space again.
Comment 2 Owen Taylor 2011-01-20 20:27:32 UTC 
Mousing into dead space will definitely be fixed in the 3.0 timeframe. I'm less sure about a configurable barriers extension.
Comment 3 Tanuva 2011-01-20 21:09:23 UTC 
The docky guys solved it the way you suggested Dan, the whole dead space has become the hot area. As I just noticed, this of course also applies to clicking notifications (which I mostly miss at the moment :) ). If it will be fixed until 3.0, everything should be fine...
Comment 4 Jason Clinton 2011-03-08 18:56:17 UTC 
*** Bug 639973 has been marked as a duplicate of this bug. ***
Comment 5 Alexander Larsson 2011-03-17 14:39:25 UTC 
This is fixed in the latest X releases with CRTC avoidance (part of the pointer barrier work).
Comment 6 Alexander Larsson 2011-03-18 12:44:53 UTC 
I tested this with a new xserver with the CRTC confinement, and this is automatically fixed (the xserver just won't let the mouse enter the dead area).

I'm closing this NOTGNOME. Eventually all distros will get this, i don't see the point in adding gnome-shell workarounds.
Comment 7 Frederic Crozat 2011-03-18 13:08:16 UTC 
FWIW, pointer barrier and CRTC confinement aren't yet part of a released X server, so for now, it requires backporting patches for server + updated xproto and libxfixes to 5.0
Comment 8 Florian Müllner 2011-03-23 17:49:19 UTC 
*** Bug 645599 has been marked as a duplicate of this bug. ***