← Back to team overview

touch-packages team mailing list archive

[Bug 1355284] Re: Switching swipe directions should reverse app spread

 

This bug was fixed in the package unity8 - 8.02+15.04.20150120~rtm-
0ubuntu1

---------------
unity8 (8.02+15.04.20150120~rtm-0ubuntu1) 14.09; urgency=medium

  [ Albert Astals ]
  * Fix going to scopes when the Manage Dash is open (LP: #1403464)

  [ Josh Arenson ]
  * Create a PhysicalKeyMapper to handle all physical/hardware keys (LP:
    #1390393)

  [ Michael Zanetti ]
  * make spread reversible (LP: #1368668, #1355284, #1368677)

  [ Nick Dedekind ]
  * Unhook Lights interface from indicator widgets
 -- Ubuntu daily release <ps-jenkins@xxxxxxxxxxxxxxxxxxx>   Tue, 20 Jan 2015 11:18:21 +0000

** Changed in: unity8 (Ubuntu RTM)
       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/1355284

Title:
  Switching swipe directions should reverse app spread

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

Bug description:
  The new app spread is gorgeous, thank you! In general we try to ensure
  reversibility of transitions - if a user starts a gesture and changes
  their mind they should be able to reverse the gesture and exit the
  transition as long as they have not lifted their finger.

  In this case, a user swiping from the right who intends to toggle
  windows but overshoots (thereby entering the spread) should be able to
  change direction, move their finger back towards the right edge,
  returning to the toggle and then to the original app if they move
  their finger all the way off the right edge.

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

  User should be in control through the whole the gesture. We want to have
  reversibility also after second commit point the same way we have for the first commit point in current implementation. 

  This has now been captured also in the right edge documentation:
  https://docs.google.com/a/canonical.com/document/d/1FC_-
  5yz5kPy_ZvTphaqxOgI5BPnALFbxRAO4eJkzlf8/edit#

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


Follow ups