Overscan gets applied when window frame is outside of the display frame.
This is a natural situation for freeform windows, so they should not
receive the overscan inset. Applying overscan insets causes the
application content to get squashed, when we resize the freeform window
and part of it is outside of the display.
Bug: 26009343
Change-Id: Ib614fb8c7170c3b6d69614b813674853e1204eef
This is the first UI iteration which contains elements for
displaying the keyboard shortcuts. Is is by no means final,
the following items (and maybe more) still need to be actioned:
* no UI for phone
* no view for system shortcuts (which contain icons)
* the shortcut items container needs a custom layout which
needs to wrap and right align elements (prototype done)
* find or build an util which can produce human readable
names of the baseCharacter and the modifiers (so far I
found a few functions, none of them good)
* not pixel-perfect
* the scrollbar does not show
* the last separator (before the DONE button) is not
visible
Change-Id: I0d191e9516ab8f4728f40b3eefe9d854249ee7a8
As an exercise for a new API candidate LocaleList class, this CL does a
mechanical refactoring to replace Locale[] with LocaleList in
KeyboardLayout class. Note that what changed in this CL is just an
implementation details that is never exposed to application developers.
One take-away from this exercise is that finding the best-match locale from
an ordered locale list is really a common pattern. Perhaps we may want
to have a guideline for this kind of situation.
Change-Id: I142379afbaf24d524ff09cf6c7ee7720150f7489
Setting the wallpaper is still synchronous: the caller blocks until any
backend cropping/manipulation has completed. There is a timeout (currently
30 seconds) on that to avoid wedging the caller arbitrarily.
Bug 25454501
Change-Id: Idca2fe1b10e4fa34d6d54865903d9a1b9e305e3c
Adding a System API for applications to access a context hub.
The API is not expected to be exposed to third party Android
applications in the medium term.
Change-Id: Ia2222317c913de6901f3912e4c89b5cfa398be85
Since the activity-alias is backed by the same code as the original
activity definition, they should both have an identical encryption
awareness. This fixes a bug where we accidentally dropped that value.
Bug: 26731340
Change-Id: I6ad615332df7d16542893a49e6997c88fc24334b
Developers using these classes can getPreferenceManager() and
explicitly set the storage location for any SharedPreferences values
persisted through it.
Bug: 26747519
Change-Id: I133045df6a69aa99f33b6b6c447f52605468b927
