Limit BigText template to a fixed number of lines.
Optimize layout of BigText and Inbox for expansion.
Bug: 6457470
Change-Id: Ib7389e16e566df9f91347ca3fdd621916a12af9b
This change allows more flexibility in target placement in MultiWaveView.
It now supports a new way of specifying chevron drawables that allows
them to be moved in directions corresponding to more than the four basic
directions (right, up, left, down).
Chevron drawables can now be updated in an overlay.
This change also adds a place holder and makes a minor tweak to the layout
on 720dp devices where the navbar buttons weren't centered.
Change-Id: Icd319ec5f276870380e27737c873e78f599ff751
TargetDrawables now have a "home" position they can be scaled about.
Added new "focused" state to TargetDrawable. This is used to distinguish between highlight and selection.
Updated target icons to use new focused state. Currently re-uses "activated" icon.
Change to event handling to allow cancel events when a target is highlighted to cause a selection.
Cleaned up MultiWaveView initialization code.
MultiWaveView animation improvements:
- new scale animation when center handle is touched.
- switched to using indices instead of foreach loops in critical path code to avoid creating temporary objects.
- updated and simplified animation code.
Change-Id: I593c021475f1644c73bdb9f84855e6a9fec7c0ab
1. Now the spinners in the time and data picker a wider therefore
easier to interact with, i.e. harder to miss accidentall.
2. Removed the scroll distance cut off user to distinguish between
fling and change by one.
3. Added visual feedback when the areas the serve as virtual buttons
in number picker are poked.
4. Removed the coeffcient that was making drap not to be one-to-one
with the scrolled distance.
5. Added some margin at the top and bottom of the spinners in
date and time pickers.
bug:6321432
Change-Id: I311c1733d1951b0563209401faa830ca70ec87cb
1. Delegating activation gestures has several issues that we should
decide how to handle if possible before allowing an accessibility
service to take over them:
A) It is needed that every view than can be clicked or long pressed on
reacts to such as a response to calling performClick and performLongPress
which is not necessary true since the view may watch the touch
events and do its own click long click detection. As a result it may
be possible that there are view a user cannot interact with in
touch exploration mode but can if not in that mode.
B) Clicking or long pressing on a different location in a view may yield
different results, for example NumberPicker. Ideally such views have
to implement AccessibilityNodeProvide which provider handles correctly
the request for click long press on virtual nodes. Some apps however
just fire different hover accessibility events when the user is over
a specific semantic portion of the view but do not provide virtual
nodes. Hence, a user will not be able to interact with such semantic
regions but the system can achieve that by sending the click/long click
at the precise location in the view that was last touch explored.
2. Adding a flag on accessibility service info to request explore by touch
mode. There is no need to put the device in this mode if node of the currently
enabled accessibility services supports it. Now the problem is inverted and
the service has to explicitly state its capability.
3. Fixing a bug where includeImportantViews was ignored for automation
services.
Change-Id: I3b29a19f24ab5e26ee29f974bbac2197614c9e2a
Bug: 6405276
- Make thumbnails bigger
- Make thumbnails higher-res
- In landscape, start the thumbnails on the right
- Fix issue where you'd sometimes see "No recent
apps" flash before the thumbnails appeared
- Fix issue where the first time recents was run
you'd see double the amount of thumbnails
Change-Id: I878caf57a955cb6a0c1b4f0a72b5b993609047f2
* Fix layout for small-screen devices in landscape.
* Properly re-enable buttons after restoring instance state.
* Scroll to the currently selected item after restoring instance
state.
* Smooth scroll to the currently selected item if the user changes
selection to an item slightly out of view.
* Place grid scroll bar outside the grid's padding.
* Make the current text read a bit more naturally.
Bug 6460135
Change-Id: Ic60330365cdd815e7517f01b36bcdc9d1c857f30
Move a bunch of dimensions around so that 7" tablets use phone-style
UI but with different margins to reduce the width.
24dp margin for portrait and 48dp margin for landscape.
Existing sw600dp values moved to sw720dp.
New sw600dp values created.
Bug: 6445803
Change-Id: I835c8f4b0423b295dd453161f4e32406e6267515
Bug 5731093
Replace TextView by EditText to make it cleaner.
Had to force the text color, although the TextAppearance should
handle it. Maybe something is wrong with the theme.
Also added a hint for consistency.
Change-Id: Icd7170a0ef3757d0313e0799873f2dd375b02f2f
This fixes several layout issues on phones and tablets with MultiWaveView.
It adds a new background scrim to be shown behind the MultiWaveView
on the navigation bar.
MultiWaveView is updated to handle gravity constraints which makes layouts
much more flexible across devices.
Change-Id: I64068f4eaa81ef6c464247049117d53432fcacbd
Bug 6428812
Change ResolverActivity to use a grid rather than a list, and present
buttons for "Use Always" and "Just Once". Use large launcher icons
when appropriate.
Change-Id: I177360a727cbc4b401ffbcea83d1b3dac1de5744
Added bitmaps for permission group icons. We had to pick either
icons for a dark or light background, and it had to be light for
settings, so the installer theme has gone back to dark.
Tweaked the permission groups to match the icons.
Redid the group priorities to make them correct (they were written
with higher priorities being less important).
Fixed bug where priority was not being used for system apps.
Change-Id: Ia3d3f0c1614a11b4cfd11682ce9e6c9f87d75c06
1. While a default target is very convenient, having two targets for the
widget on a phone takes too much space and the apps do not have room
to add other essential affordances to the action bar. Making the default
activity show only of the screen is large enough - the action bar
accommodates at least four targets i.e. 500dip.
2. Fixed a bug where changing the backing model of an ActivityChooserView
when the view is not shown did not remove the observer for the old
model, hence the View can get into a state where it responds to changes
of two models while presenting only one. Also in such a case the view
would leak since the singleton model will keep a handle to it.
3. Updated the documentation of share action provider to explain how a
a developer can change the backing history file and refresh the UI
based on the historical data in that file.
bug:6447692
Change-Id: Id5c9e54cd5df322ded8574ba028cb680e628243b
