issue 132366412
-> First, we shouldn't accept flings when the delegate has intercepted. This prevents any situation
where both are triggered.
-> Modified the slop to be the standard 8dp. This acts as a standalone fix because
it means that there are no situations where we cross all apps slop before assistant slop.
ie. in a purely vertical gesture from the corner, without this change, it's possible to trigger
all apps instead of Assistant.
Change-Id: I39e3d8a525e165024399d9802d4cc1d7ae329ee6
Disabled apps were always accessibility-marked like "Disabled Messenger"
With introduction of dots, this degraded, the the "Disabled" part was
never added.
Restoring the old behavior here.
Bug: 129036789
Change-Id: Icb97ea9a190643449d90f558a78039df30c53cbf
This should help avoiding situations when an icon is intermittently
found in the suggested row vs. the recycler.
Change-Id: I71b17caa5f827999f0901d5c4d4348de7e16f053
Calls SystemUIProxy.onGestureCompletion for a completed gesture
(either drag or fling) and passes in the velocity (0 for drags).
Bug: 132356358
Test: manual
Change-Id: I080adc401e19a6141627d1806b425056f7eefcbd
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
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
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
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
Adam Cohen
TreeHugger Robot
Miranda Kephart
vadimt
Sunny Goyal
Jon Miranda
Zak Cohen
Winson Chung
Tony
Hyunyoung Song