- Initial changes to show a history view within Overview (behind tuner
flag)
- Restoring the task view dim in the stack
Change-Id: I0503d11768736c86f3145942404391dfacd0ddd6
- Fixed issue with max scroll position being placed beyond the max
scroll if the task height is larger than the stack height.
- Fixed issue with single task offsets being calculated incorrectly
Change-Id: I3cb1ecf2c13de7196bd68cd4f9d9f4f4736ed3ce
When dismissing the docked stack, we animate the divider to position
-12dp, so the full-screen stack is exactly full-screen when the dismiss
animation is done. Previously, this was prevented by window manager.
Allow it to fix the animation.
Change-Id: Iee4505023dc3f6907d56851965b156235f9f97f2
Add an optional parameter in moveTaskToDockedStack to supply an
initial rect to be used when creating the dockeds tack. Pass in
the adjusted rect when dragging up from the navbar so it doesn't
flicker anymore.
Change-Id: Ieb3c8c73b9e2a769a2ec6270bd76a713201a2aed
- Previously on MNC, they would return the same result regardless who
the calling user is.
- Now they properly take DO user-id into account. Meaning, they'll
always return false and null respectively, if the calling user doesn't
run device owner.
- Note isDeviceOwnerApp() is a public API and getDeviceOwner() is
a system API. Meaning we're changing the behavior or non-private
APIs.
- Also cleaned up hidden APIs, and gave them explicit suffixes
to avoid confusion. Bundled code should prefer them for clarity.
Now we have:
* APIs that work cross-users: They all require MANAGE_USERS.
boolean isDeviceOwnerAppOnAnyUser(String packageName)
ComponentName getDeviceOwnerComponentOnAnyUser()
int getDeviceOwnerUserId()
boolean isDeviceOwnedByDeviceOwner()
String getDeviceOwnerNameOnAnyUser()
* APIs that work within user. No permissions are required.
boolean isDeviceOwnerAppOnCallingUser(String packageName)
ComponentName getDeviceOwnerComponentOnCallingUser()
Bug 24676413
Change-Id: I751a907c7aaf7b019335d67065d183236effaa80
* changes:
Create PrintDiscoverySession for future print services
Update printer availability when printSpooler is paused. This makes the window update syncronously when in multi-window mode.
We are not saving the state of this fragment on onSaveState,
so its Okay to loose state while confirming the transaction.
bug:25847358
Change-Id: I2f6587d528b2d8b8f24a83954cc896a6ff514996
- When going from freeform -> overview, hide all freeform tasks until
the final frame of the enter transition, if the stack we are
launching to/from is in the freeform stack
- When going from overview -> freeform, hide all freeform tasks after
the first frame of the exit transition, if we are launching a task
in the freeform stack
- Separate the dragging gesture from the freeform launch visibility
Bug: 25842568
Change-Id: Ibcd17a02eeb70244ac73f599b8c23c71d22f73fd
- Allow ignoring alt-key release when interacting via touch while
alt-tab is pressed (ag/814903)
- Cancel window animations only if the stack scrolls via alt-tab
(ag/809873)
- Fixing issue with old task load plan being consumed if user alt-tabs
before Recents is resumed (ag/811354)
- Canceling enter animations when the stack scrolls (ag/814461)
Change-Id: I7450f0a280571e98212f321b1e61219d149fed65
- Adding “focused” stack state to support paging
- Changing the paging to match UX spec (only auto-page after the first
tap)
- Removing old header focus animation
Change-Id: Id72825b8a1b1c0a2238ee184a6695b13c1d8cb1c
- Moving to a couple piecewise curves to define the various overview
layout states. Added a new state for focus (to be used in follow up
CL) to control paging of overview from the nav bar button. This
allows us to control the visible range of items on the curve, and
to better fit other UI controls around the stack.
- Removed the scaling of the tasks in the stack
- Also refactoring parametric curve to just use the system Path
Change-Id: I4108da77986d86896576e36fa8f31189d6fcb6f3
SettingsProvider used to prevent any changes to certain settings
when the corresponding user restriction is set, which isn't really what
these restrictions mean.
Even if a user restriction is set, it should still changing in the more
restricting direction.
Also stop setting "" to LOCATION_PROVIDERS_ALLOWED, which will simply
be ignored.
Bug 25614198
Change-Id: Ifa8edc2927e21e6c6174620c8c874c86c1dc0f75