AmbientState is a global state for the algorithm of the
StackScroller. Dimmed and which child is activated was moved
into this state. Further, scale and dimmed is also a
StackScrollState and animated in StackStateAnimator.
Change-Id: Ia68131cee62b2e0005f55ea6dc400d149ec15278
This also includes a new (very WIP) interaction to get to quick
settings, with clumping the cards and a scrollable container with
the cards and the bottom QS part in it.
Change-Id: Ib073bb0174cddcf60347a5e3bb474fb3b6385bcf
It was previously possible to get into undesired states when closing
the shade and clicking on it in midtransition. This was also triggered
when double tapping a card.
Bug: 14130526
Change-Id: I6b73f348dba4ee21d2401004176a9c6cc0c59745
When an animation was already running, the calculation of the
new duration was wrong. We are now also starting the animation
instantly instead of waiting for the next frame.
Also improved the scrolling performance, which was lagging behind by one frame
Change-Id: I25d6e6eedf33d94f2f90bdc39d863955c707370c
Add a flag to indicate that the IME should be shown. This follows
the continuous ime notification boolean, and if there are multiple
input methods to choose from enabled. This way the notification
and navigation button show up under the same circumstances (but
not on the same devices).
Change-Id: Ia6a2253061f1876f4bcc511de48c1078e9d96be5
Animations are now only triggered when absolutely needed.
In addition, the notifications are now not clipped anymore when starting
a drag on them and the notification below the dragged one is fadded in if
necessary.
Change-Id: I80e8b3ea8fb48505edfb3cace6176dfa00c5a659
- Falling back to default transition if we don't have a thumbnail (Bug 14589475)
- Tweaking over scroll to prevent scrolling past a certain point (Bug 14582630)
- Fixing issue with missing top padding in the stack view
- Adding some shadowing to distinguish similar cards from each other
Refactor the camera affordance into a reusable view. This change
also swaps the asset for the camera affordance.
Bug: 14488709
Change-Id: I0633614f6a1ea81faa37923f748af3c635e64a52
Also make the bouncer less translucent, so it looks better when
a user double-clicks on a notification (because it is now shown
behind, so we need more background protection).
Bug: 14059777
Change-Id: I2538b0e04ddc25c25a03c65c8a5bd7855720bbf2
When there are hardware keys getNavigationBarView() returns null,
this just checks before setting the visibility.
Bug: 14491311
Change-Id: I2ea8b62b1dfe05ca09636870b37dff184730369e
Because the actual height is the different as the laid out one, we
need to filter the touch events here.
Change-Id: I6abd3fb0fffe275c2b83e7c48df1dd866499a28c
Starts expanding the card if it is expandable. If it's not, we
rubberband the expansion a lot. After the threshold has been reached,
we scale all the notifications up and make it fully white and opaque.
Change-Id: I9ecd020ca263b0f84e87fd6ab2332519ac5e9984
This state can be either reached by tapping the more card or dragging
down on any card. In this state, the shade is fully interactive, but
the phone is stil locked. This state can only be enterred if
redaction is off but security is on. If redaction is on, we will show
the bouncer instead and go to the normal shade.
Bug: 14161523
Change-Id: I95ca0991745ffc11ed1028581e3da15265c12ae5
Adds button in the same location as the menu button and overrides
it when present. The setNavigationHintIconHints lets it know when
the button should be shown.
Bug: 14257632
Change-Id: Ia80de7fd2390cd8b083e37cbe58b7ee53555e619
