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
Use scale listeners to track each other's icon scale to match them.
Test: go to recents and long press icon
Fixes: 110789415
Change-Id: I9bba3130ecf1d099db9708c84e709d16f5906c36
While swipe-up animation is running, the user can quickly start
another touch gesture. In that case we keep the recents transtion active
and proxy all touch events to launcher.
Bug: 110901700
Change-Id: Ie3b448dfea00473082dc9143423d3596504a3fcc
* changes:
[automerger] Workaround for flicker between handoff from app to task view am: 35a6848fa8
Workaround for flicker between handoff from app to task view
- 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
There is no events from nav bar to send to drag layer until crossing the touch
slop on move. If up occurs, sending the touch down event will clear floating
objects such as the folders.
Change-Id: I6095506f505535e04d59c403e539f37e27295470
Fixes: 111008382
Test: open folder, touch an empty space on nav bar
> Separating the task icon animation and setter into 2 separate methods and calling each appropriately
> Using taskId instead of TaskView for ignoreSet as taskView can be reassigned
Bug: 110893730
Change-Id: I7bc958e53becffdf633766373b257ead2eeef2ad
- We can request the locked orientation for quickscrub only when we
start quickscrub
Bug: 80500702
Change-Id: I2e83ff916f92959fccf79f1d6b987806338512f5
Separating InvarantDeviceProfile out of LauncherAppState and creating
LauncherAppState only when it is actually used
Change-Id: I2ee55f53cae01f11203f94675bb5f70c65ad2b9d
Round the y and x values to get correct position without showing a small
line when opening the task menu.
Test: increase the display and font size to large, go to overview and
tap icon
Fixes: 110415497
Change-Id: Ia41378863fb08fc72f5cd14b40f45769ab612d22
> Using {packageName} instead of hardcoding com.android.launcher3 in AndroidManifest.xml
for strings which are dependent on packageName
> Adding proguard rule to prevent obfuscating any overridable class
> Making it easier to extend SettingsActivity by overriding the fragment class
Change-Id: I5668c3f33b4cf20ad01d7f54b3d79cc0d268d391
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
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
> Preloading assist data after the touch interaction is complete
> Fixing swipe-up callbacks called in case of quickscrub
Bug: 110532258
Change-Id: I472884ec96be877db5f38098fd0165d464e836ed
* changes:
[automerger] Allow clear all button in overview be clickable if visible am: 330a634648
Allow clear all button in overview be clickable if visible
Android Build Merger (Role)
Tony Wickham
Winson Chung
Matthew Ng
Sunny Goyal
TreeHugger Robot
Hyunyoung Song
Adam Cohen
Jonathan Miranda