1. Views may setSystemUiVisibility() to recommend that
the system chrome (status bar or other UI) show or hide
itself. (This functionality was previously available only
via the FLAG_FULLSCREEN window flag for some SystemUI
implementations.)
2. Views may register a OnSystemUiVisibilityChangedListener
on a view, and find out when the system UI actually
appears or disappears, allowing apps to coordinate the
appearance of their own UI if desired.
Bug: 3241144
Change-Id: Ia1758d94099182d49a1e3688ea2738ae4995b829
We're still not stretching the panel smoothly yet; this just
fades the panels in and out at the right times.
Bug: 3323063
Change-Id: I6eb87c44726f48f39fab77710b1ffe5d0783d588
- Contract date field to avoid collision with clock.
- Tune the clock font size in bar & panel.
- Better vertical alignment of bar icons.
Change-Id: I491c8678eec8dd3e5236121cc08583e2b8c79fc2
Similarly, touches in the glow area surrounding the panel
title no longer switch into settings mode.
Bug: 3339023
Change-Id: I142e500a55ecfca24082c28e75e5e71c1524ad56
This might fix the bug where tapping outside the notification panel doesn't close it.
I'm not 100% sure because I can't reproduce this on-demand, but I think it's possible for
onSizeChanged to race with the animations and we end up with a bad rectangle. The time
I did see it happen was tapping above the title area right after canceling a notification,
so that could explain it I think.
Bug: 3339023
Change-Id: Ic3a7f4c059e7bf6f30b864a371a0912a6414edb7
3362464 API REVIEW: android.content potpourri
3362445 API REVIEW: Fragment transaction stuff
3362428 API REVIEW: Fragment stuff
3362418 API REVIEW: Loader stuff
3362414 API REVIEW: android.content.pm.ActivityInfo
Change-Id: I6475421a4735759b458acb67df4380cc6234f147
This updates the animation and fixes a few bugs with showing
and hiding recents as well as tweaks from UX in animation
timing, effects and the background protector.
Change-Id: I1c57e566408c7b732a0c902e27125951d0277322
I think what was happening is that it was using a different layout but we were trying to reapply the
RemoveViews because of some bad boolean logic. This fixes that, and adds some better debugging that
might show us what else is happening.
Bug: 3298062
Change-Id: I0984f24cb2960166c79b9f2cc7c6a98bd75e17ba
There will be, in the future, a flag (View.DRAG_FLAG_GLOBAL) that means
for the drag to be cross-application. For now that flag constant is @hide
and furthermore the server-side implementation strips it, enforcing
local-only drags.
Change-Id: I8db840480ab90e18a5b8ecf29d62b4e6eafd405e
