Tapping the ticker will still launch the notification's
contentIntent, but tapping anywhere else in the bar will
immediately hide the ticker.
Bug: 3365129
Change-Id: Ic1abd38fd4c5bdf32f3586b4e4aa5b833b11a9bd
I also tuned the animation parameters a bit to get things to
look just a tiny bit smoother. The first run is still jerky
but it's not jumping all over the place in the wrong
direction.
Bug: 3404950
Change-Id: Id10c52f227e6d2db428dc860097023560d154356
* changes:
Make keyguard also ask to turn the back button off, now that it is controlled separately.
Allow independent control of the back and the other navigation buttons.
Allow the status bar disable flags to be used as View's system ui visibility fields.
(Tapping on the lights out shadow will now immediately show
the system bar in addition to informing the StatusBarManager
that the system UI chrome should be shown. This allows an
ACTION_DOWN to reach the back/home/whatever buttons even if
it was originally invoked when the lights were out.)
Bug: 3400262
Change-Id: I9b1b5240c003ad510fd65cb606728850d705ef33
(Previous behavior: the tap would pass through to the clock,
which would open the shade. Only sometimes it wouldn't,
because you'd have hit the left-hand-side of the ticker
where there's no clock underneath. So this fixes that too.)
Additionally, tapping the ticker will now immediately
dismiss the ticker.
Bug: 3365129
Change-Id: Ic641184c518b18d799a560c8da6b4c5844c912de
ANR doesn't seem to be happening any more.
BUG: 3142881
This reverts commit c597ba8e9ad08ac628271b4498c27eda74c6c86c.
Change-Id: Ib6eb407c700bc9a8460f49394ec71d75d14588e2
Signed-off-by: Mike Lockwood <lockwood@android.com>
- Move notification icons and clock down by 1dp
- Make control panel background translucent to match
notification panel
Bug: 3394785
Change-Id: I0988fa595e2cf014b9bf31d102b428cfb2ce8732
- Includes the correct ticker background image, finally
- Confines the ticker height to 48dp (status bar height)
- Aligns the ticker to the bottom of the screen
Bug: 3361133
Change-Id: I9497f29d2b4c1cbcb195f0e66393f6db97d01ee2
The calculation for determine the content view's bounds
was mistakenly using the position of the view in the immediate
parent (glow view), which wrapped it exactly in the vertical
direction. The code now uses the glow view's vertical
position in its parent to determine the position.
Change-Id: I07768eb3446fde851699de1c1d4e958bc16d98bb
