Fixes: 123641382
Test: Swipe up and hold from app when SWIPE_HOME is enabled or swipe up from app when it's not
Change-Id: I1bd35b1b96d66a3996f9b24c9a7e896535fa1ca0
This reverts commit 3a4f503e5d.
Reason for revert: need TouchInteractionService to be direct boot aware for the merge
Change-Id: I5b3c651df77f8df1d5f07245b062f2384cd760a0
This reverts commit 0a13878b96.
Reason for revert: We decided to get launcher dimensions differently in the short-term
Change-Id: I875f0dab36922e7f85f4dff7af1ab1f22a9c4bd8
In case events come out of order, the list is not properly initialized
which can lead to missing invalid states
Bug: 127282292
Change-Id: I3b4784b8e3eec890e80e62c2ea613e1ba84b6c95
- Needed to account for the preview bounds (similar to BubbleTextView icon
bounds)
- Also needed to update the bitmap shift amount so that it is re-centered
- Moved ShiftedBitmapDrawable to its own class in graphics package
Bug: 123900446
Change-Id: Ifa9e3f688e55d017cf86a0285f5cdb1b014f01e6
Before, we just didn't scale or translate when entering spring loaded
state. That worked when dragging from home, but when dragging from all
apps it meant that the hotseat kept its translation from the transition
to all apps. Now we always move the hotseat to scale 1 and translation 0
when going to spring loaded mode.
Change-Id: I0630d5bb899e37e2ab01516adfc1b7e6f8a9e42a
Overview chips are constructed in AiAi and inserted into a Launcher
container (similar to what's done for the SuggestView). This CL
(and its sibling) remove the dependency on the NavBarHint plugin
for chip hint data, and instead obtain the information from AiAi.
BUG: 124390101
Change-Id: I07beb79dba2edaafb231b03e70b647ae211b5c1b
- Move the hotseat alongside workspace instead of on top of all apps in xml layout
- Set pivot point of hotseat to match the workspace's, and apply the same scale
- Translate the hotseat with the workspace instead of all apps
- SpringLoadedState does not scale or translate the hotseat
Change-Id: Ic45fe99f83f0e0012afa78073d9577e65da444e2
When home key is pressed, we skip the schedular check as it comes
in onNewIntent (explicitIntent).
Bug: 118441555
Change-Id: I934bb14e4d188cf61faed0360c3f6d7cac8d2fed
- Apply the bounded current scroll to the overscroll instead of assuming
the max scroll (on the last tick, the overscroll amount can be zero,
causing us to shift to the max scroll until the next draw)
Bug: 126767319
Change-Id: Ia60ecb0c3f18e68d0c91620aa79b21df72c213cf
In case of normal restart we were never applying the NORMAL state and
so various state properties didn't start with correct default values.
We generally get insets after start which reapplies the state and
fixes this issue but that is not always the case.
Bug: 126416861
Bug: 118441555
Change-Id: Iaa178556618f8a49197187d0820d8b8afdc73378
With adaptive icons, we can have FloatingIconView match the shape
and size of the closing window, regardless of the icon shape.
FloatingIconView starts off as a rounded rect (same corners as task view)
and then morphs into the icon shape using FolderShape#createRevealAnimator
in reverse.
Decided to add FeatureFlag.ADAPTIVE_ICON_WINDOW_ANIM since there are still
some issues with folders, badges, and a visible jump when swapping the
FloatingIconView with the original icon.
Bug: 123900446
Change-Id: I94969eea6d5f4b932a84a11eb403611276042b46
