* changes:
[automerger] Using dragHandle for workspace padding calculation instead of pageIndicator am: 08ef66789b
Using dragHandle for workspace padding calculation instead of pageIndicator
* Animates LauncherRootView instead of DragLayer to avoids the flashing that
can occur when the overlay callback also changes the DragLayer alpha.
* To avoid the scrim's hard line: we hide it and then fade it in later.
* Launcher animation was wrong in landscape mode.
Change-Id: I7673228f5ed8bb72d7393f3d0769577b262f286f
* changes:
[automerger] Fixing crash when cancelAnimaiton happens while we are aboutto enter long-swipe am: 1d82dd4d12
Fixing crash when cancelAnimaiton happens while we are aboutto enter long-swipe
App-to-recents via square button now generates an event (sysui_latency: [1,<latency>]) for latency tests.
Bug: 72967764
Test: atest google/perf/app-transition/sysui-latency-test
Change-Id: Iae9e3112ab28d98ec2c11111f259010692e7fc7a
- Based on workspace page instead of workspace (takes padding into
account)
- Checks that width != 0 so we don't divide by 0
Bug: 79526164
Change-Id: I25d92a04550aa34abab7e9e1f93c93dbccd61752
> PageIndicator is a 1dp indicator which does not contribute in any padding calculations
Bug: 79111591
Change-Id: I4d8be0149da2b3f14593ae71ca037ffe3885d9be
* changes:
[automerger] Removing extra binder call on state or visibility change am: 6b4b9b5d71
Removing extra binder call on state or visibility change
* changes:
[automerger] Use device api level if first_api_level is not set. Bug: 79429532 am: a30bf371e4
Use device api level if first_api_level is not set. Bug: 79429532
- Don't lock when making WM calls (only lock when resetting), and use own
executor since the background executor is fixed to only two threads and
other things can be running on them already (like task loading).
Bug: 78585335
Change-Id: I73dfc380dd99908cfc30ff7c164a9677a5a126e0
- Don't lock when making WM calls (only lock when resetting), and use own
executor since the background executor is fixed to only two threads and
other things can be running on them already (like task loading).
Bug: 78585335
Change-Id: I56e24fbbdeb3b673837982df3fa67e485d03b3b2
> Caret is only visible when the accessibility is enabled
> It is visible in NOTMAL and OVERVIEW state and moves out of the
scrim along with the scrim.
> Acts as an accessible target for various options
Bug: 78172350
Bug: 79215734
Change-Id: I8a968b67e36901859649546295f6491d49cc9ce9
State handlers can now specify atomic and non-atomic components of
their animations to states, which can be specified when creating a
new animation. There is now one atomic animation, when going from
NORMAL to OVERVIEW (and in reverse):
- RecentsViewStateController's animation (scale/alpha) is all atomic
- WorkspaceStateTransitionAnimation has atomic and non-atomic:
- Hotseat and workspace alpha is atomic, as is workspace scale
- Everything else (scrim, translation, qsb and drag handle alpha) is
non-atomic
- All apps progress is non-atomic
Also simplified dragging through overview; no longer pulls against you,
so we use an OvershootInterpolator when flinging instead of our custom
interpolator for the spring effect.
Bug: 76449024
Bug: 78089840
Change-Id: Iafac84d0c2b99ee9cf9dd5b30e2218286713b449