The following methods are now supported:
getResourceEntryName
getResourcePackageName
getResourceTypeName
getResourceName
Bug: http://b.android.com/181872
Change-Id: If06b5e0687ab6f8cb20ab77f339870dd08a84ce1
This changes the current API given app feedback received. In order to use
keycodes as well as chars we also must implement a mapping of Keycodes to
Display labels as only keys with a single char representation are provided
by KeyCharacterMap.
Bug: 27409783
Change-Id: I3da653adc4b8cbc66a4d1aa24a5f9181f71e83c3
The "default network tracking" request is somewhere between a listen
and a request, in previous semantics. It is more like a listen in that
it doesn't cause any network to be brought up, but also like a request
in that will only get callbacks about a single network at a time (not
all networks that might match).
This change minimally splits the NetworkRequest types into 3: LISTEN,
REQUEST, and TRACK_DEFAULT.
Change-Id: I2d113b2f6eed526a7808592bce0118260a56f77c
- TaskStackLayoutAlgorithm currently depends on the launch state to
calculate the right bounds, which means that the launch state has to
be set before the call to getThumbnailTransitionActivityOptions().
When double-tapping quickly, we would use the old launch state which
would cause us to calculate the wrong bounds.
Change-Id: I5dd9f38b49652a6ac8bed4b9fd4ffa02dfe90289
* changes:
Tweaking scroll-to-launch task animation.
Completely removing dead code related to history view.
Completely removing dead code related to search widget.
Iterating on stack layout
- This CL repurposes the history button above the stack to a more
generic “stack action” button in preparation for a future change.
Bug: 27742174
Change-Id: I1da274bf88c77bdc09d91072683b2ea7ca022432
- Tweaking initial layout to show more of the next task
- Bounding the width of the stack to the smallest display edge length
- Fixing issue where the screen pinning button was not shown when
entering recents from home, and the task view clip state was not
restored correctly for tasks in front of the launch task.
- Fixing issue where there was no alpha during the transition to/from
home
- Refactoring and removing unused dimens, and moved remaining layout
calculation logic out of RecentsConfiguration.
- Fixing small regression in finding task anchor scroll points. This
caused tasks to be animated strangely when swiping to dismiss and
the task had an override task progress.
- Fixing several regressions in drag and drop due to override progresses
Change-Id: I1eac1dcea19e502bc7fe6362011b38977e3f3d6d
Previously when determining the next stack to focus to in
multi-window mode, if it is the home stack we just bring it
forward and focus on whatever the home task/activity is.
We should be checking the returnToTask type of the activity/task
that is going away to determine which task in the home stack
we should return to.
Bug: 27776008
Change-Id: I1a864c96b2ef276d2ddeafcb627a2b6a825e2ce7
