** Changed in: ayatana-design
       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/1064945

Title:
  Multi-monitor - Add 'sticky edges deactivated for number of
  milliseconds after the user breaks the barrier' variable that works
  when the Launcher set to 'auto-hide' and sticky edges set to 'off'

Status in Ayatana Design:
  Fix Released
Status in Unity:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ayatana-design/+bug/1064945/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to