** Changed in: unity/6.0
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/987955
Title:
Multimonitor, Launcher - When the Launcher is set to autohide and
'Sticky edges' are turned off, 'Launcher Edge Stop Overcome Pressure'
seems to be broken when revealing the Launcher
Status in Ayatana Design:
Fix Committed
Status in Unity:
Fix Released
Status in Unity 6.0 series:
Fix Released
Status in “unity” package in Ubuntu:
Fix Committed
Status in “unity” source package in Precise:
Fix Released
Bug description:
[Test Case]
1. Have a multi-monitor environment (at least 2 monitors enabled)
2. Enable Launcher auto-hide in g-c-c
3. Make sure you have the launcher set to appear on all monitors
4. Disable sticky-edges
5. Move your mouse from the right-most screen to the screen to the left
-> Verify that there is some pressure needed to move from one screen to
another, caused by the fact that the Launcher auto-hide is enabled
[Regression Potential]
Trivial change, no other regression potential.
Original description:
Currently if the sticky edges are disabled, they are *all* disabled.
However what should happen is that if 'sticky edges' is disabled AND
the launcher is set to auto-hide, the sticky edges should remain
active on a single edge (where the launcher is) from a single
direction (the direction the pointer has to travel to reveal the
Launcher)
What currently happens:
When the Launcher is set to autohide and 'Sticky edges' are turned
off, 'Launcher Edge Stop Overcome Pressure' seems to be broken when
revealing the Launcher. It is switched off on all edges
What should happen:
When the Launcher is set to autohide and 'Sticky edges' are turned
off, the 'Launcher Edge Stop Overcome Pressure' should continue to be
active *only* as part of the launcher reveal action. e.g. if the user
moves the pointer from the right to left to reveal the Launcher it
should be triggered and the monitor edge, but if the user moves the
pointer from left to right (or down to up, or up to down) across a
monitor border it should not be triggered.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/987955/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp