Use focused task id for getting task size
When getting the selected task size, look at the focused task id, not
the running task id.
I believe this was a typo from the original change.
Bug: 190399315
Test: Local build and flash and run
Change-Id: Ice92e0562765f4f0142e27da0c38140df4c11425
- Add mNavBarButtonAlpha to TaskbarStateHandler, and set it to the inverse of the taskbar alpha.
- Add mPendingSetNavButtonAlpha for when setNavBarButtonAlpha() is called before mSystemUiProxy is initialized.
Test: Go between various launcher states and ensure nav bar only shows up when taskbar hides.
Bug: 187353581
Change-Id: I4b79280d686c787e9128e753070ec591d1ab2e4d
- With live tile enabled, the race between destroying the task and
killing the process is more evident since the app may not get
stopped at all. For now, when dismissing, defer removing the
task until we've finished the recents animation to allow the
app to be stopped accordingly
Bug: 184899234
Test: Dismiss the task from overview, check that the app gets
lifecycle events
Change-Id: Ib3ea479643d65859fe4cd580b4c347b87130a69d
Merged-In: Ib3ea479643d65859fe4cd580b4c347b87130a69d
The App window will be under Launcher, so we can't actually blur
launcher at that time, otherwise the live window will also be blurred.
Test: manual
Bug: 189207458
Change-Id: Ie07449d29d3b0dc60d3787b6d32aa9e46e0bb613
- With live tile enabled, the race between destroying the task and
killing the process is more evident since the app may not get
stopped at all. For now, when dismissing, defer removing the
task until we've finished the recents animation to allow the
app to be stopped accordingly
Bug: 184899234
Test: Dismiss the task from overview, check that the app gets
lifecycle events
Change-Id: Ib3ea479643d65859fe4cd580b4c347b87130a69d
> Calculating the hotseat padding statically
> Animating taskbar views individually when animating to home
instead of a layout animation
> Moving all navbar buttons to a separate layout/controller and independent
of Launcher
> Fixing RTL layout for taskbar and nav bar
Bug: 187353581
Test: Manual
Change-Id: If21696f38beee328f553e467394776a8e8ed4c3e
When one handed mode activated, user swipe-up to exit usually
cross over the NavBar region, and then invoke TouchController
intercept touch event to trigger All Apps drawer on Home.
To enhanced the UX of gesture conflict of exit OHM & All Apps,
notify TouchController throught LauncherActivityInterface,
and Launcher dispatch onOneHandedModeStateChanged() event to
all mTouchControllers in DragLayer that touchController can
adjust the touch slop by it's SingleAxisSwipeDetector.
Test: manual trigger One handed mode and swipe-up to exit
Test: monitor minDisplacement of SingleAxisSwipeDetector
OHM activated : touchSlop x multiplier
OHM deactivated : touchSlop x 1
Test: check All Apps doesn't mis-trigger when exit one handed mode
Bug: 186235522
Change-Id: I7b9e6e7fa898231697d1866186a5f9b1717a9aa3
There is a case when one handed mode triggered(Activated), all apps
drawer is very easy to trigger while user swipe up around NavBar
region to exit one handed mode. Since System Gesture monitor regsion
is small on screen bottom, swipe-up gesture usually cross over NavBar
monitor region and invoke launcher touch controller intercept touch
event and introduce unexpectedly trigger all apps drawer.
Adding onOneHandedModeStateChanged(boolean activated) for controller
be able to adjust the touch slop by multiplier, we can set a larger
multiplier when the visible window size translate become smaller
and make swipe gesture not too sensitive.
Test: manual swipe up to swich "home <-> all apps" and monitor
minDisplacement of SingleAxisSwipeDetector
Test: Trigger one handed mode and swipe up to exit one handed mode
check the minDisplacement of SingleAxisSwipeDetector
Bug: 186235522
Change-Id: I9729cd408d85b2b22582bf800e28d1471fc06980
Wei Sheng Shih
zakcohen
Pat Manning
Tony Wickham
TreeHugger Robot
Winson Chung
Sunny Goyal
Lucas Dupin
Vadim Tryshev
Yogisha Dixit
Vinit Nayak
Alex Chau
Bill Lin
Bill Yi