touch-packages team mailing list archive

[Launchpad Bug Tracker <1368287@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package unity8 - 8.01+15.04.20141202-0ubuntu1

---------------
unity8 (8.01+15.04.20141202-0ubuntu1) vivid; urgency=low

  [ Michael Terry ]
  * Make sure that there is no window of opportunity for swiping away
    greeter before the lockscreen appears.
  * Don't allow dragging the greeter out from the left edge if it's
    hidden there. (LP: #1372952)

  [ Michał Sawicz ]
  * Move from Theme colour to direct UbuntuColors.orange for activity
    indicator and preview buttons

  [ Albert Astals ]
  * Use QImageReader not to load the image into memory twice (LP:
    #1384374)
  * Don't create the whole current scope delegates, just height * 3 (LP:
    #1384393, #1384374)
  * Make CroppedImageSizer async
  * Use ubuntu::connectivity::NetworkingStatus instead of
    QNetworkConfigurationManager
  * Compile with Qt 5.4 (LP: #1395636)

  [ Michael Zanetti ]
  * close previews and temp scopes on left edge/BFB (LP: #1391798)
  * make spread reversible (LP: #1368668, #1355284, #1368677)

  [ Andrea Cimitan ]
  * Different drag behaviour for not closable apps in spread (LP:
    #1368287)

  [ Daniel d'Andrada ]
  * Make UnityTestCase.touchFlick properly map event coordinates
 -- Ubuntu daily release <ps-jenkins@xxxxxxxxxxxxxxxxxxx>   Tue, 02 Dec 2014 09:26:49 +0000

** Changed in: unity8 (Ubuntu)
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1368287

Title:
  [App switcher] Different drag behaviour between items that can and
  cannot be closed

Status in the base for Ubuntu mobile products:
  New
Status in Ubuntu UX bugs:
  Fix Committed
Status in unity8 package in Ubuntu:
  Fix Released
Status in unity8 package in Ubuntu RTM:
  New

Bug description:
  Drag to close is a great feature in application spread. In user
  testing it had a great success rate and users understood it and knew
  how to use it. The problem is the Dash item that's part of the spread
  but is the only item which cannot be closed. Currently the Dash item
  drag movement is similar to the movement of the items that actually
  can be closed.

  We want to make Dash drag different from others by restricting the
  movement while still responding to user's drag.

  ------------------------------------------------------------
  Desired solution

  Use restriction algorithm for dash item so that it moves along the
  drag but soon starts restricting the movement indicating that it's an
  item that cannot be closed.

  Here is quite nice elastic function that can be used:
  function elastic( currentPosition, limit ) {
      return limit * ( 1 - Math.pow( ( limit - 1 ) / limit, currentPosition ) )
  }

  Where:
  limit is the highest value that ever can be returned by the function
  current position is the value to be limited

  It's a bit hard to describe the parameters, therefore I created a prototype that should explain the usage. 
  Find it from: lp:~willow-team/willow/elasticRestriction

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1368287/+subscriptions