Change-Id: Ib7b01562c1f15524f0e3599864a95ad9fb9d4be6

Merge "Fix bug where FolderIcon stays visible during swipe up to home animation." into ub-launcher3-qt-dev

Change-Id: Ia2969688d9ae4c89a2da45eb6361f4476e1877ec

- Fixes clipping issues.
- Fixes badge being shifted.

Bug: 124510042
Change-Id: I2520d963fb2041a049650c2b8c12ddb3de7b8d87

Bug: 126744445
Test: manual
Change-Id: Id00ffac4581bbbe5dfd73a63b05c4512394745c1

Bug: 132917885
Change-Id: Ib702fd17fecff980db2e1d00f05cd055bcc3185a

This can happen when opening an app from a folder, and then immediately
swiping up back to home.

This happens because when we swipe up to go home, there's a race condition
where the folder close animation finishes and sets the FolderIcon to VISIBLE
right before FloatingIconView sets it to INVISIBLE.

To fix it, in OverviewState#onStateEnabled we call
AbstractFloatingView#closeAllOpenViews(animate=false). Then we added logic
to cancel any Folder closing animation (which there is,
from WindowTransformSwipeHandler#onLauncherStart) and to just close the
folder right then and there.

Bug: 132588097
Change-Id: I4379431815e7cbddede5ea0213fe9323f001484b

Change-Id: Iff9706d078515a280ae7cf9d8c9dae8d269e1939

Change-Id: I9c2ac12d81d3b04e1a29f6c2a1f2e32fff76de7f

Change-Id: Idb7962e62c0c95f8a50792e9342562c6d8b6ba42

Change-Id: I2b8d65885f83154f7500adb520b1eed1da5c4a4e

If the centermost task is null or doesn't yet have thumbnail data,
don't use its sysui flags - continue using the window we're swiping
from instead.

Bug: 132898688
Change-Id: I202937d8aa01ee24ef01693d9594c4929e6bd314

If the second touch happens outside the swipe region, for eg when the user
is using a different gesture like pinch-to-zoom, do not capture the
input events

Bug: 132916535
Change-Id: I59df3831b96689586a2a684bf11805d42f1cb1d9

- When tasks are restored, they don't have a valid display id yet,
  but they will still be started on the default display and should
  have the same options until proven otherwise.

Bug: 132892578
Change-Id: I8ba0a976bd5682fbcda72ca1a98bf2517eb31312

Change-Id: I03d5ea5aac618eba7e0e5a1555e45a165918bb60

Instead of faking recents scaling up when swiping down on a task,
actually scale it up. This is more consistent with what we do
for scaling to/from fullscreen elsewhere, and cleans up some code.

Bug: 130020567
Change-Id: I1a07813468d9a66f8f4e7b5d3d9a191b565f165c

- BackgroundAppState sets this to 1, all other states set it to 0
- QuickSwitchState extends BackgroundAppState, and calculations for
  fullscreen scale/translation are moved to BackgroundAppState
- Move fullscreen progress logic out of WindowTransformSwipeHandler
  and into the launcher activity controller, which uses the new
  RecentsView.FULLSCREEN_PROGRESS property to animate it

Bug: 130020567
Change-Id: If6265fcce3749050be354742e7d2c418d11ee9bb

- Set to match the workspace padding on the opposite side of the
  screen.

Bug: 130521490
Change-Id: I26fd71bb146c56a647397a040dbbac9d1556c3fe

Change-Id: I90a8753975538ab9864591a37a7d366e1222f2d8

If the user drags almost all the way to gesture completion and
then flings, the haptic got triggered twice: first for the drag,
and then once the fling was registered. This checks whether the
assistant was already invoked before triggering the fling
invocation.

Bug: 132908798
Test: manual
Change-Id: Ibeed7279b8db32527490a0e11b8e5f0761187bbf

This fix allows for a clean tradeoff between the FIV and the original icon
in all icon shapes.

Bug: 130292844
Change-Id: Ief2eec2673161e0f9d32d8710713a1f01880040d

Bug: 118758696

Change-Id: I66cd36cda495d339e0c2550f0957e3fbcddca477