- Moving header bar event handling to TaskViewHeader
- Removing several proxy callbacks from RecentsView
Change-Id: I7dc99a7b580c1beaa93216d2b29c94246b35ec5d
- Initial change to use the event bus by dispatching
package events directly to the TaskStackViews instead
of passing them down the view hierarchy manually.
Change-Id: Ic68df9eeefb79eab8ded84b74264a93719b40643
isUserSwitcherEnabled now returns false if multi-user is disabled(
supportsMultipleUsers() returns false).
Removed GUEST_USER_ENABLED setting and replaced with DPM.getGuestUserDisabled
check. It currently always returns false, but will be replaced with an actual
policy check.
Bug: 17571233
Change-Id: I41853e8b321b2537952cac5d92e88bfdb8cbd9a8
It is possible for an external process (e.g. sys-ui) to call into
WM to get the bounds of a stack in between the construction of the
DisplayContent object and SystemServer telling WM that the display
is ready. Incorrect bounds would be returned to the caller in this
case since the baseDisplayWidth/Height is only set when the displayReady
call is made.
We now initialize the base display information when the DisplayContent
object is created so any call to get the logical display rect of the
display will always return the right bounds. This should be okay as the
display manager is initialized way before window manager.
Bug: 24505761
Change-Id: Iebd688ad8f4c08556846fcebb543e58bd2c01414
- Follow up to ag/778718, with the resources split up, we can now update
the task bounds before starting recents.
- Also removing the multi-window check for transitions in/out of recents
Change-Id: Id4a6d4cfa9d98ca3ecf5f237573bf240f232de54
In a new split system user model, owner of a restricted profile is not limited
to just user0. restrictedProfileParentId field should be used to get an owner.
Bug: 22950929
Change-Id: I928319a9450e543972237a42267eb2404e117c83
- We can no longer make assumptions about the ability to
get resources for the RecentsActivity before the activity
is launched (the configuration of the launched activity
can differ than the current configuration if a window
is docked). As such, we reduce RecentsConfiguration
to the set of values that are context agnostic, or can
be calculated directly given an application context.
This ensures that we will continue to be able to compute
the target task bounds given any context.
Change-Id: I423c90635eb294aa2d78a6f56771b98ee2b9d5e4
Only shows if translation is available, follow-up
I3e883eeca002e86d4df30c2b238e18bd63bbddea to show in
all locales.
Bug: 24167496
Change-Id: I667cde69e5d5f8aec8ac9fd105bbfb7e118ced64
