* changes:
[automerger] Fixing disabled filter is not applied to the foregound layer when dragging an icon am: b6d292d788
Fixing disabled filter is not applied to the foregound layer when dragging an icon
* 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
Previously we were ending the atomic animation with the assumption
that it should be complete/almost complete by the time you drag to
the next state. However, it is very easy to drag quickly enough where
that assumption doesn't hold, and thus you just see the atomic
animation pop to the end (i.e. recents showing without animation).
Now instead of ending the atomic animation, we let it continue. But
because the new state animation will have an atomic component that
interferes with the still playing atomic animation, we have to
control the atomic component separately; we control the non-atomic
components until the atomic animation ends, at which point we create
a separate controller to control the atomic components.
Bug: 76449024
Change-Id: Ia4bf19e26d0838f952d9e500fbdd8aba19856a41
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
* changes:
[automerger] Increase REORDER_TIMEOUT to make it easier for users to create/add to folder. am: 217f0ca2d9
Increase REORDER_TIMEOUT to make it easier for users to create/add to folder.
* changes:
[automerger] Enforce Swipe Up gesture to be enabled based on the shipped SDK version am: 2a8f265ab0
Enforce Swipe Up gesture to be enabled based on the shipped SDK version
* changes:
[automerger] Using surface rotation instead of insets to determine seascape configuration am: 59d086c3ce
Using surface rotation instead of insets to determine seascape configuration
Sunny Goyal
TreeHugger Robot
Android Build Merger (Role)
Vadim Tryshev
Hyunyoung Song
Tracy Zhou
Tony Wickham
Winson Chung
android-build-team Robot
Jon Miranda
Mehdi Alizadeh