Specifically, when switching from right to left edge, the
animation disappeared. This change forces the animation
to restart whenever you switch to another tutorial.
Bug: 148542211
Change-Id: Ie74c636a4afd1018c7c8e6998a1e7a176bf8099e
(cherry picked from commit e725b6fe56)
- Due to tasks only being loaded in the task list and not in the
task hierarchy, ensure that we listen to the task list callback
to invalidate the cached list as well.
Bug: 144892997
Change-Id: I0aa2ac0e629b8883410ebafbdc4ca2d5d9bc0fca
Launcher can now receive onTaskAppeared callback from
RecentsAnimationController to get remote animation target when in quick
switch mode.
Note: This CL just demonstrates how to receive callback and then
calling removeTask & finish recents animation,
in order to really improve quick switch flicking, launcher side needs
to implement the rest of logic to animate task's remote animation target
to make task switching more smoothly.
Bug: 152480470
Test: WIP
Change-Id: Id0371db7339cfe84942cc905a89b0a2c1fab62ec
(cherry picked from commit bec41bc5b9)
SysUi can then adjust things like disabling
the edge back gesture region or re-drawing the
home handle in the correct positions.
Fixes: 150250451
Test: Tested quickswitch manually with
test apps fixed to different rotations.
Ensured back only showed when rotation of
touch and display matched.
Change-Id: Ie4ea3063835a09fc12ab1d4f8b504b3a9555fa9b
> Also avoids additional binder call on resume/pause
> Removes a system API which needs to be mocked for robo tests
Change-Id: I23d0cba62c17f7659121c53d1804df40f5069005
- Whenever the delegate consumer sets itself as active, it will cancel
the base consumers which can cause onConsumerInactive() which will
clear the active consumer. Instead, we should only clear the active
consumer, and in the case where isConsumerDetachedFromGesture() is
checked, only check the active consumer before resetting.
ie.
base ic (detached) -> on touch up (do nothing) -> onConsumerInactive (active == base) -> reset
base ic (detached), wrapped ic (active) -> onConsumerInactive (active != base) -> on touch up (active == wrapped) -> reset
base ic (detached, active), wrapped ic -> on touch up (do nothing) -> onConsumerInactive (active == base) -> reset
base ic (not detached) -> on touch up (active == base) -> reset
base ic (not detached), wrapped ic (active) -> onConsumerInactive (active != base) -> on touch up (active == wrapped) -> reset
base ic (not detached, active), wrapped ic -> on touch up (active == base) -> reset
Change-Id: I2d623c501d9c9799dadcf2005f34e1e0062c113f
- Change drawable to match specs, using ShadowDrawable to
add shadow when necessary based on workspace theme.
- New drawable is 18dp by 6dp; add support for different
width vs height, and decouple from workspace page
indicator (which is still 24dp tall).
Bug: 151768994
Change-Id: Icfd0eac197ebc4d1f5bb799f8538c4bd99d800cd
Adds the back gesture panel directly to the fragment
View hierarchy rather than a separate Window.
Bug: 148542211
Change-Id: I196a72d29217308a5bdb78fdcff1face5d475379
Bug: 144953948
Bug: 137777105
The new lite proto builder is used to send two types of logging to statsd
1) Snapshot logging
2) App launch, task launch, task dismiss
Statsd will be connected once platform CL is submitted
Change-Id: If606cee5288fe4bd6c522605ae84eb0f24174f5b
Before, we did this by extending the window/launcher animation to
match the scroller duration. But now that we are using springs to
control the scroller, that duration is not really accurate. So
instead, we now let the window/launcher move at its own pace, and
wait for both that animation and the scroller to finish before
calling onSettledOnEndTarget().
Bug: 147302669
Change-Id: I37a9dd3eea17ebe663c33c3a4478b1b53a63dcc2
- When we have multiple wrapped input consumers, mConsumer will be
set to the wrapper while the caller can actually be the input
consumer being delegated to (ie. other activity ic). So we should
clear the consumer state if the caller is anywhere in the IC
hierarchy. This results in a separate issue where mGesture
could be cleared during onConsumerAboutToBeSwitched() before being
passed to the new consumer, so make a copy of the previous state
just for passing to the new consumer.
Bug: 152318829
Change-Id: I4afcef5b18aa772889e9104f3977887893f174ea
- Previous refactoring meant that we were always fetching the running
task to update the gesture state, even when you touch down in an
area that is not in the gesture region (which is unnecessary).
Also only transforming touch events (currently causes allocations)
when we are actually handling a gesture.
Change-Id: I32e21c3e4d7113a782afce593711d9df62551bc8
Andy Wickham
TreeHugger Robot
Winson Chung
lumark
Tony Wickham
Vinit Nayak
vadimt
Sunny Goyal
Becky Qiu
Tracy Zhou
Hyunyoung Song
Sreyas
Samuel Fufa
Josh Tsuji