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

Bug #1368287 reported by Vesa Rautiainen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Canonical System Image
Fix Released
High
Unassigned
Ubuntu UX
Fix Released
High
Vesa Rautiainen
unity8 (Ubuntu)
Fix Released
High
Andrea Cimitan
unity8 (Ubuntu RTM)
Fix Released
High
Michael Zanetti

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

Tags: ota-1

Related branches

Vesa Rautiainen (vesar)
Changed in ubuntu-ux:
importance: Undecided → High
importance: High → Medium
assignee: nobody → Vesa Rautiainen (vesar)
Vesa Rautiainen (vesar)
tags: added: ota-1
Changed in ubuntu-ux:
importance: Medium → High
summary: - [Apps switcher] Different drag behaviour between items that can and
+ [App switcher] Different drag behaviour between items that can and
cannot be closed
Changed in ubuntu-ux:
status: New → Triaged
Vesa Rautiainen (vesar)
Changed in ubuntu-ux:
status: Triaged → Fix Committed
kevin gunn (kgunn72)
Changed in unity8 (Ubuntu):
assignee: nobody → Andrea Cimitan (cimi)
importance: Undecided → High
status: New → Triaged
kevin gunn (kgunn72)
Changed in unity8 (Ubuntu RTM):
assignee: nobody → Andrea Cimitan (cimi)
importance: Undecided → High
status: New → Triaged
Andrea Cimitan (cimi)
Changed in unity8 (Ubuntu):
status: Triaged → In Progress
Changed in unity8 (Ubuntu RTM):
status: Triaged → In Progress
Michał Sawicz (saviq)
Changed in unity8 (Ubuntu RTM):
status: In Progress → New
assignee: Andrea Cimitan (cimi) → nobody
Revision history for this message
Launchpad Janitor (janitor) wrote :

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 <email address hidden> Tue, 02 Dec 2014 09:26:49 +0000

Changed in unity8 (Ubuntu):
status: In Progress → Fix Released
Changed in canonical-devices-system-image:
status: New → In Progress
Michał Sawicz (saviq)
Changed in unity8 (Ubuntu RTM):
milestone: none → 14.09-ota-1
status: New → Triaged
Changed in unity8 (Ubuntu RTM):
assignee: nobody → Michael Zanetti (mzanetti)
status: Triaged → In Progress
Changed in canonical-devices-system-image:
importance: Undecided → High
milestone: none → ww03-2015
Revision history for this message
Michał Sawicz (saviq) wrote :

The fix for this was just released as unity8_8.02+15.04.20141218~rtm-0ubuntu1.

Changed in unity8 (Ubuntu RTM):
status: In Progress → Fix Released
Changed in canonical-devices-system-image:
status: In Progress → Fix Released
Vesa Rautiainen (vesar)
Changed in ubuntu-ux:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.