The clause used there was using a reused value of a motion event
and therefore not trigger, even if it should have.
Also added a clause which this was actually used for to remove
the long press callback when using the inline settings slider.
Bug: 27352426
Change-Id: I9c432eeb354d7d5e72b375cfc5ead9e04a4e6c81
- Changing task view thumbnail layout. In portrait, scale the thumbnail
to width for portrait screenshots, and apply the same scale to
landscape screenshots. In landscape, scale screenshots up to 1:1, and
tweak the app transition to clip the sides instead of scaling.
In both orientations, fill with the background color in the remaining
space.
- Moving some resources related to the title bar to be calculated
programmatically so that we can have different header bar sizes which
completely overlap the action bar in the screenshot in each
orientation.
- Constraining the task stack width in landscape to portrait
Bug: 27504677
Change-Id: Ic9b6fdde6dd728d9f2d20a8b89c05b3a350edfbf
The CL adds a handler for FUSE_WRITE command which invokes a Java
handler.
BUG=23093747
Change-Id: I1903fca6b5663e6241ad540a89fe812310ba6810
(cherry picked from commit 35693da25af11583053d4af6a70d4acbf446978d)
Bonus: null advanced keys produced a exception deep in the print
spooler. Hence prevent null keys on the surface from now on.
Bug: 27716355
Change-Id: I3c064956f4e670cd7091437ade06605aa8d797b0
Currently used for a number of tests. May also be useful for 3rd-party
apps using VPN in some manner or another.
Bug: 27700919
Bug: 26887434
Change-Id: I4d269954265a2590499e20150f009fe437c8078f
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
- 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
- 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
