| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Bug: 65187090
Change-Id: Ica5b10e640cf4ab752055da2f4e352680ab26391
|
|
|
|
| |
Change-Id: Ibf48d6015d808f86bc79ccf64e3077eb5b6ccaff
|
|
|
|
|
|
|
| |
This prevents the caller app from taking over the focus while animation
it running.
Change-Id: I51b6673c59e848c263727502dee90504ed3a2162
|
|
|
|
|
| |
Bug: 34766840
Change-Id: Ib29d7d4b53ab99cdf3ff253976ef55345729487b
|
|
|
|
|
|
|
|
|
|
|
|
| |
the drag source image
> Using common code for pending item drag (WidgetContainerView and PinItemDragListener)
> Adding a shortcut-circuit in Workspace when a pendingItem can create a shortcut
directly. Previously the multi-window drop was routing through onActivityResult which
was causing some state information to be lost.
Bug: 33584624
Change-Id: I0259870032185713caa9bff27092dbae6ce91199
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
On long pressing, the confirmation activity starts a system
drag-n-drop and focuses the launcher activity. We then drive
the launcher drag controller using the system drag event
Caveats:
> We use a transparent preview for system drag and drop and use
a view inside launcher for actual preview. This gives us better
control over various animations.
> The parameters for drag operation are passed to the Launcher
activity using the intent. Since onNewIntent and onDragEvent
come at different times and are not associated, a random uuid
is used as mime-type to match the drag event with intent params
> If the workspace is locked (eg, loader is running) the drag
operation is simply dropped. Will be imporved in follow up cls
Bug: 33584624
Change-Id: I0bb5b25b690f86b6af31a14e11beb669fcb3a281
|
|
Also fixing some platform API changes in PinItemRequestCompat
Bug: 33584624
Change-Id: I255829f0079f1a3967bf8d6a337da12c890eb7ec
|