Error prone complains when trying to merge launcher3 code to platform pi-dev.
"This looks like a test method but is not run; please add @Test and @Ignore,
or, if this is a helper method, reduce its visibility."
Output:
Executing tasks: [:assembleGoogleDebug, :assembleGoogleDebugAndroidTest]
Gradle build finished in 1s 631ms
Tests Ignored: 1 passed, 4 ignored
Bug: 78589564
Change-Id: Icde57fd8307e1ef409822d1417f629cd1aaa57ba
There is also a deadzone area around the clear all button to tap easier.
Test: start overview click anywhere that is not the shelf or task
Change-Id: I187ff264444da542aca111b57d94c8199f5a0384
Fixes: 110232233
Error prone complains when trying to merge launcher3 code to platform pi-dev.
"This looks like a test method but is not run; please add @Test and @Ignore,
or, if this is a helper method, reduce its visibility."
Change-Id: I95f55b95d8f7752c9c941f0828ca22d6427528c6
Before, we were just controlling the components as far as we had left,
which was fine since they are just a subtle effect anyway. But now that
we don't fade out until the very end, this means that long swiping from
home usually kept recents in the background during the entire swipe and
then abruptly disappear after letting go. Now we make sure the entire
atomic animation plays by the time we reach all apps, so recents will
fade out in all cases.
Bug: 79867407
Change-Id: I7cb6790d9055bc76b4b73ed761604042a308c987
> Preloading assist data after the touch interaction is complete
> Fixing swipe-up callbacks called in case of quickscrub
Bug: 110532258
Change-Id: I472884ec96be877db5f38098fd0165d464e836ed
Go devices will not want QS.
Bug: 77490347, 110425849, 109932837
Test: Manual, Launcher is no longer crashing
Change-Id: I1a1e0540beeab04927802156be26098139710f30
- All apps content fades in quickly so that icons are opaque by the time
they are on screen
- Recents fades out late so that we don't see it as translucent while
the transition is continuing (the translucent icon top of tranclucent
task view looks bad, for instance)
- Fix colored scrim that appears over recents - was using 0 to 1 instead
of 255
Bug: 79867407
Change-Id: I4f50423157f7870c8d0708f586a72e3e5a7b6559
* Extend page indicator so that its centered within the gap between
the workspace items and hotseat.
* Decrease the amount of extra space we allot to the hotseat.
* Add the extra space to the hotseat bottom padding so that the hotseat icons
are aligned to the top of the hotseat.
Bug: 78589630
Change-Id: I78c619a757d9d248874216e93376ad4ba18c8e50
The "spring" is actually three sequential animations: 1) a slide,
2) an oscillation, and 3) a settle.
Bug: 109828964
Change-Id: I0a2c55f877446a6408952a1201636760283be57b
Test: enter overview, make sure clear all button is invisible, try to
tap its location
Fixes: 110432640
Change-Id: I7531e4c6cfdcc9a29d98da24a73c32b8080e013c
This fix attaches the AnimatorListenerAdapter on the parent AnimatorSet
to ensure all animations are complete before removing the floating view.
Bug: 110156760
Change-Id: I56638d745227e414583fa47a202c9aaa33874baa
These sources didn't pass a normal CR, and mustn't be used in prod. The
goal of landing them is to start in-lab flakiness tests ASAP. A normal
code review will follow after landing cleanup CLs.
Bug: 110103162
Test: Running TaplTests suite
Change-Id: I051591c9af7822d4cbae4261e66563f1ccc1cfcc