@Trevino; no problem, I have opened a new bug, see bug #1064945
I have now marked this bug as fix released
** Changed in: ayatana-design
Status: Fix Committed => Fix Released
** Changed in: unity (Ubuntu)
Status: Triaged => Fix Released
** Changed in: unity
Status: Triaged => Fix Released
** Tags removed: udp
** Tags added: reviewedbydesignq
--
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/1020058
Title:
Multi-monitor - Add 'sticky edges deactivated for number of
milliseconds after the user breaks the barrier' variable
Status in Ayatana Design:
Fix Released
Status in Unity:
Fix Released
Status in “unity” package in Ubuntu:
Fix Released
Bug description:
We have tested the fix, and while it is an improvement the one of the
important use cases is not yet solved. To reproduce:
1. Using a computer with two monitors, set the Launcher to auto-hide
and sticky edges to 'off'
2. Set the 'sticky edges deactivated for number of milliseconds after
the user breaks the barrier' variable in CCSM to "1000ms"
3. Move the pointer over the boundary from the left screen to the
right screen slowly, and then try to move it back again (within 1
second).
What currently happens: the pointer gets caught on the Launcher reveal
edge resistance on the left edge of the right monitor
What should happen: There should be no resistance when the pointer
comes back across the barrier because the barrier was already broken
inside 1000ms when the pointer moved from the left monitor to the
right monitor.
Also: set the value of the variable to 1000ms
--------------------------------
Add 'sticky edges deactivated for number of milliseconds after the
user breaks the barrier' variable to CCSM. This variable would de-
activate sticky edges for a set number of milliseconds every time
after the user's pointer moves from one monitor to another.
In addition to the 1000ms barrier switch off timer, the barrier should
also only be switched off for only one crossing e.g. so that if the
user tries to correct an accidental crossing of the barrier they can
do so with no resistance, but after correcting this accidental
crossing the barrier is switched on even if 1000ms has not yet
elapsed.
The idea behind this behaviour is to allow the user to course-correct
after they have broken through the barrier the first time.
Don't change any of the default values for the time being; once this
is implemented we will user test and experiment with different values
before deciding on whether we should change the default behaviour.
Note: Before working on this bug it is worth checking with Jason Smith
to see if he has already implemented some of this.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/1020058/+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
