- Reduce slop for gestural mode (and apply multiplier to slop
at checktime)
- When quickswitch threshold is passed, reduce the total movement
check and reduce the velocity needed to fling to the next page
to accommodate short swipes
- Use touch slop to determine scrolling in paged view, and only
use paging slop to determine flinging to the next page (when
easy flings are disabled (which is the default))
Bug: 157165240
Test: Ensure the flings in normal overview/paged views don't change,
check short flings from quickswitching
Change-Id: Idd04ce23f53c06759e84ac8ad73cf2cc6dff6975
We were setting mGestureState = DEFAULT_STATE when touching outside
of the swipe region. Instead, we should only set mGestureState when
starting a new gesture, and only set it to DEFAULT_STATE on reset.
This also makes it clearer that mGestureState always refers to the
current gesture state, rather than sometimes being the current
gesture and sometimes being the previous gesture depending on
where it was used. Now previousGestureState is passed when needed.
Bug: 159494933
Change-Id: Ib62278b7c591ca4c6b99b26e058a34772e6cec2a
Screenshot: https://screenshot.googleplex.com/TckWKGYWwHW
Note: Shortcut predictions will not be cached.
Bug: 159500320
Test: Manual
Change-Id: Id8ec81544bddb8be87a5e748fd9f9e93aaaf8fea
It flakes when one of the tests starts calculator while there zero
activities in the system.
Bug: 143488140
Change-Id: Id9d350f0de8a83eb50e35e9efa4226b8d45ca641
This is a workaround until we can support app transitions when starting
an activity in mw mode.
Bug: 158613217
Change-Id: I843d6669722c543728ab532e1c4fbd4643f6f135
- Reverts change from ag/11900651 that deferred setting
mRecentsViewScrollLinked = true
- Instead, setCurrentPage(mCurrentPage) after updating layout rotation
to ensure we recompute page scrolls before using them
Test:
- Auto rotate on, home rotation off, open Calculator in landscape,
swipe up slowly and ensure it never turns invisible
- Quick switch from Calculator to Clock, start swiping directly up
immediately after settling on Clock, ensure Calculator window
remains at its scroll position to the side (b/159461591)
Fixes: 159461591
Change-Id: Iab92963cc6c33df42b77f5ccfa3932382e8f869a
Sends AppTargetEvent with action launch and container CONTAINER_OVERVIEW to AppPredictor when user launches app form recents.
Bug: 155996363
Test: Manual
Change-Id: I3eb38f5737ecaeb07e59db460e8d809416132825
> Using common code for Launcher and recents for insets dispatching
> Fixing recents auto closing when there is no running task
Bug: 158750568
Bug: 159133601
Change-Id: Iee25c603a77a1ac546ada1840f3afaf5797b8802
Feedback wasn't working, also Share wasn't showing its preview.
Bug: 159122067
Test: built and run locally
Change-Id: Iccea012a8fc0009a6a980f6233f42c4e7619f4ec
Sometimes other methods modify things like icon scale that setting
the fullscreen progress should override.
Test: open Calculator, open Clock, quick switch to Calculator and
ensure its task icon is not showing
Bug: 157105795
Change-Id: Iaed3e42f540fdff3648e9db7e6d7dc0b0d0a75df
- This was only used in RecentsView#resetTaskVisuals() anyway
- Previously resetVisualProperties() just called resetViewTransforms()
plus setFullscreenProgress(0) and setModalness(0)
- The latter 2, specificially setFullscreenProgress(0) led to problems
such as the bug below. Instead, we should reset to the current
mFullscreenProgress and mTaskModalness.
Bug: task view sometimes shifted up during quick switch
Steps:
- Do the quick switch gesture very quickly
- At the start of the gesture, we call getTasks(), which calls
applyLoadPlan() asynchronously
- applyLoadPlan() calls resetTaskVisuals(), so if this happened
after the gesture ended, we would setFullscreenProgress(0) on all
the task views, hence the upwards shift (if the gesture was still in
progress, it would reapply the real fullscreen progress)
Fixes: 157105795
Change-Id: Idb9d91ff89701d726838b47f955d4300f5ef13bd
TreeHugger Robot
Winson Chung
Tony Wickham
Samuel Fufa
Hyunyoung Song
vadimt
thiruram
Sreyas
Jon Miranda
Zak Cohen
Sunny Goyal
Bill Lin