SplitScreen task shortcut was written with an expectation that only one
instance would be created at a time.
No that it's used by Accessibility, SplitScreen may be asked to provide
multiple shortcuts at a time for multiple tasks, and they share same
mTaskView.
Fixing this.
Bug: 78094307
Test: Manual
Change-Id: Ib440ca862b0677ec4a012ec9f2a225183b2c91f4
This caused regressions in flip-order mode.
Will figure our later what should replace it when clear-all is enabled.
Bug: 72222505
Test: Manual
Change-Id: Ie3d65f550935a26efa8e8e31594dbe8f35ba1f71
- Snapshots can now be translucent which means that we always have to draw
the background for translucent apps
Bug: 77813801
Change-Id: I70bd77aa56ee7988e2af1b602884739837478c39
It’s an initial implementation, i.e. no fancy effects.
It shares a parent (LauncherRecentsViewContainer) with RecentsView.
The button is centered in clear_all_button_container, which gets
positioned programmatically to the right of the last task. (RTL polish
will be a separate CL as well).
Bug: 72222505
Change-Id: Ia912908a93a30c2f51450ccf0f97c7495e7916d5
Test: Manual
Call onIntercept and ontouch direclty, so that the touch is only
handled by touch handlers
Bug: 77912191
Change-Id: I8b583da2394282c757348818470dbb4bee095b33
The icon grid was reappearing at the end of the animation, causing
slower frame draws at the end of the animation, possibly leading
to jank.
Fix this by waiting with resetting the alpha until the whole
animation is done.
Test: Open/close apps
Bug: 75985430
Change-Id: I8fa62c5f648335ce9d4c4450d52c46465e2d08bf
(cherry picked from commit 197808681d)
We now animate the dim alpha at the same time as the task icon.
I also clarified the dim alpha by inverting it where it is used in
TaskThumbnailView. Otherwise, we have to pass 1 - dimAlpha everywhere,
which is confusing and verbose.
Bug: 76170043
Change-Id: If8c01300993a0e5543b0650d44daaa143592b96e
(cherry picked from commit 291bfd9c95)
> Only hiding the task associated with the current task, instead of hiding all tasks
> Maintaining a state for hidden task so that it does not get reset when alpha is changed due
to some other reason.
Bug: 77830202
Change-Id: I202e99b153c6f9e3a8d9c68d6844672b3bff41e9
Otherwise we'd be stuck using the old touch controllers until DragLayer
is setup again (e.g. launcher is killed).
Bug: 77921826
Change-Id: I8aac6fc453839902cb2d99279a6bd1549ee17d79
> If launcher already started, creating the state transition only after threshold crossed, so that previous animations are not cancelled
> Not posting animaiton callbacks at the front of the queue, as that sometimes causes it get executed before onNewIntent
> Farking the activity as forceInvisible while launching an opaque app, so that quickly pressing home/back runs the reverse animation
> Not running state animations when force-invisible is true
Bug: 77830325
Bug: 77898806
Change-Id: I50a7e915ca35fd6aeb284c8f321ecca74396fe98
I find this less confusing, as the controller is also used in portrait
mode when swipe down is disabled.
Change-Id: Ifd6b4453a1b59e1f8305c1461d89ed99de2fe7d6
