* Number of hotseat icons matches number of workspace columns.
* Evenly space out the workspace icons.
Bug: 111617973
Change-Id: Ia80e6354c8d449f2a397db5fd432cebc9f23027f
When swiping up to overview from an app, we scale down RecentsView in
launcher, synchronized with the app window. In rare cases, however,
there may not be any TaskViews in launcher, so we should just ignore
the launcher component in this case. For example, this happens in
LockTask mode.
Bug: 110703110
Change-Id: Ib6f836581a3e12babf4e26e272b77bb529f86fd4
- When hitting the home button, we may be loading high-res thumbnails
unnecessarily since the high-res loader is already enabled when
Launcher is started.
Bug: 111515602
Bug: 111156069
Change-Id: I367993b4ddf653b816355df005c745caed5e794a
Tablets generally have larger cell sizes (relative to phones, and relative to
the icon sizes with the cells). By increasing the distance from 55% to 75% of
icon size, it is easier for users to meet the folder creation threshold before
the icon reorder timeout is triggered.
Bug: 110796219
Change-Id: I8264390b8510340f4062e05ec12d0755e93a80d8
- Defer finishing the recents animation for a couple frames until the
frame has likely been pushed to sf and drawn, otherwise the reparenting
of the app surface may happen before the task view is visible in
Launcher.
Bug: 111299394
Test: Swipe up repeatedly from an app
Change-Id: I627dc085a5e376436b2b8eb5841c45fd36deff42
Instead of using an OvershootInterpolator, we adjust the end progress to > 1 and
add a second interpolator to settle back to 1. That way, even if the animation runs
starting very late, e.g. 1.0, it still has room to overshoot. We use this same
OvershootParams class to calculate an overshoot for a blocked long fling as well.
Bug: 109709720
Change-Id: I43152237e4350f93e7c462c22e68d09d05c1dd57
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