Bug 180431

Summary: Panel unhiding after auto hide does not work on the smaller of 2 screens
Product: [Unmaintained] plasma4 Reporter: Daniel Thaler <Daniel>
Component: containment-panelAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: aseigo, asraniel, notmart
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Daniel Thaler 2009-01-12 09:59:35 UTC 
Version:           KDE 4.1.96 (4.2 rc1) (using Devel)
Compiler:          gcc 4.3.2 
OS:                Linux
Installed from:    Compiled sources

I'm using 2 screens - the built-in screen of my notebook (1440x900) and an external TFT @1600x1200. The desktop is stretched across both screens.

I have the panel at the bottom of the notebook screen. When I set the panel to auto-hide it is almost impossible to get it back, because unhiding apparently requires the the mouse pointer be right at the lower edge of the screen, a 1 pixel wide target.

This would not be a problem but for the fact that I can move the cursor *below* the edge of the screen on that display because the other display is 300px higher.

Effectively this renders auto-hiding unusable on the smaller screen.

I would like to request that the panel should be shown whenever the mouse is below it, too.

Extra info: I'm running Arch Linux, and KDE is v 4.1.96 as packed by Arch.
Comment 1 Marco Martin 2009-01-12 21:21:32 UTC 
could be easily achieved by expanding the unhide trigger to be down the screenin this case...
but, controls to check if this screen is not the largest one could perhaps be complex and maybe in some edge-case that expanded geometry could interfere with the actual geometry of another screen? (not sure about that)
Comment 2 Aaron J. Seigo 2009-01-15 07:42:01 UTC 
yes, the fubar here is that the mouse can go below the edge of the screen. that's a Don't Do It kind of thing, and the x configuration ought to be fixed.

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