- Scale up adjacent recent tasks and translate away from center
- Workspace card instead recenters in the screen
- Translate hotseat offscreen
Clicking on one of the adjacent tasks will scale it up to the
center of the screen while the center and other adjacent task
parallax to the right beneath it.
Change-Id: If96eec987c100458b8444a6cd698ec7bf6e6ba6b
before marking the ViewOnDrawExecutor as completed.
Also fixing model writer not updated on rotation
Change-Id: I5ecd7ac865b939ffa4c02afe892bd773d9f275c3
- If there is any delay in launcher draw, then we will finish the
transition and hide the app window before launcher has had a chance to
draw the task view with the updated snapshot.
Change-Id: I81c5b467f32520fd7474bde0e89819336292e84f
In some cases, eventQueue could be running on the background thread where as
the invalidate happens on the UI thread, which could cause race conditions in
touch consumer
Change-Id: Iebd84238eb2b5d6774beaa3bc21afdeb09e62561
When the animation is cancelled, if remove the pending handler
(incase it has not executed yet) and revert back to the old
state if it has executed.
Change-Id: Iddc305aaaeae78c06cbf6c1c271254409cc1487d
Bug: 73242451
Test: Swipe up over back button, ensure that we don't start the animation
until the threshold is crossed
Change-Id: If84c39370428f8ea5bf9d5f7110d17227f00ccc0
Instead of setting the icon scale to 0 in showTask(), which is
called whenever we get a new intent, only set it to 0 when
starting the swipe up gesture.
Change-Id: I657a1c5763c60b65e28f453ffe854ae8dab83bbc
- Fix back button flickering when returning to NORMAL state instead of
finishing a gesture to, say, ALL_APPS. This is achieved by posting
changes to the back visibility on the UI thread (binder calls are
posted on the background thread).
- Restore back button when touch service reconnects (in case we were
forced into an app when launcher is force-stopped, for instance).
Change-Id: I3731ee43d66965ce7cd8cf026174aabfe2d5c56c
* Animations appear snappier by using new interpolators
ie. new EXAGGERATED_EASE and updated AGGRESSIVE_EASE_IN_OUT
* Updated app icon/window alpha to make the motion/synchronization clearer.
Bug: 70220260
Change-Id: Ib05efc7f58d53b070e58f682f30651e31f9b3524
> EventQueue is only accessed on the binder thread
> For every new touch down, we use a new event queue to prevent race conditions
> All event hendling are serialized by event queue (including quick switch/scrub)
> Using state handlers for quick scrub
Bug: 73356768
Change-Id: Idde33a348270b8167a087129f177d5d2b54f5822
- Always launch workspace card if it's focused when quick scrub ends
- Previously it would get stuck if quick scrub end was called on
a background thread (since it was trying to touch RecentsView)
- Prevent user from being able to get to the workspace card if
starting quick scrub from an app by introducing bounds checking
- Prevent getting stuck in overview when ending quick scrub
- There was a race condition where the task wouldn't launch if
the animation to recents hadn't yet finished. Now there is a
callback to ensure that launchTask() is always called after.
Bug: 70180755
Change-Id: I3c131011634880a97de8c2935c3ebdab26494b48
These records are required by “Transition Delay - Hot Launch From
Recents” test. It doesn’t look at transition times for this event. They
are just a part of its expected sequence of events.
I generate transition delay times as zeroes because no one is looking at
them.
Bug: 72967764
Test: atest google/perf/app-transition/app-transition-from-recents-trace
Change-Id: I4a5b76b95c6c4b54e7fb620951342a3ed8564aed
