- add accessibility descriptions to camera and search light
- add new onClick handler to simplify launching search and camera
- plumb camera launch through KeyguardService interface
Fixes bug 10914360
Change-Id: Ic85eda9afadba7381be78b477180f7204030cd17
Use a transition-drawable to crossfade between the gradient and
solid color backgrounds, avoiding custom onDraw.
Rename colors to their final names. Since both bars now receive the
gradient treatment, centralize in base BarTransitions.
Bug:10602521
Change-Id: Id094fa1767eabab88a3709d6026c23858c83fb5b
This fixes a bug where the code would pop up SearchPanelView and never
close it. The result is that the overlapping window would absorb all input
events and effectively prevent the user from entering their pin/pattern/password.
The fix is to replace ImageView with KeyButtonView to make the behavior consistent
with how it's handle in home screen.
Fixes bug 7520075
Change-Id: I461bf2844c023fd7a2dffca1177cc5951f30dba0
For now, each time the dead zone captures a touch, it will
flash to let you know that's what happened. We should
probably turn this off before shipping.
Note also that this currently only expands the navbar on
ACTION_DOWN elsewhere in the UI (because this is the only
time ACTION_OUTSIDE is generated); this isn't perfect and
we'll need to do some mucking about with the input system to
get information about ongoing drags or additional pointers
down, but this CL is a good start and introduces the general
mechanism for expanding and contracting the dead zone.
Change-Id: I43e63aed1e541fd07d83fde4d66bcb5be89b69d2
It's too easy to press if it's *all* the way to the right,
though, so there a 2dp margin separating it from the bezel.
Bug: 6399312
Change-Id: If4ebcd4cfcee0c667bcc6142af86c04445f41fea
There's now no dead space between them. Also, increase the
visual size of the nav icons by 30% (just a quick resample
of the current artwork, to be replaced by custom-drawn
graphics at 130%).
The background glow looks kind of comical right now.
Bug: 6381833
Change-Id: I03ef0ea64a9e953f9f2b29cc03097d250ff52134
Devices between 600 and 719dp will now use the two-bar
(phone) SystemUI layout, or something like it, derived from
PhoneStatusBar. Devices above 720dp will use the system bar
from TabletStatusBar.
However, this distinction is not to be made based on dp, at
least, not by the SystemUI; the goal is to drive most of
this switch from the window manager. Therefore most of
SystemUI's sw600dp resources have been folded into the main
set of resources (renaming them to avoid collisions where
appropriate). This allows SystemUI to choose which set of
resources to use entirely by switching status bar
components, entirely independent of Configuration.
(For some resources, particularly around recents, it seemed
more expeditious to keep relying on the device
configuration, so those resources have been bumped up to
sw720dp.)
Bug: 6297838
Change-Id: I3f5414a6a718bdc83f51930d6878cdf97df48c9c
