This mode has the remove icon on the left side, so flinging to the
left makes more sense. But flinging up still works in either case.
Change-Id: I7ab40776b67659026f03f81efd43fae3375b5ba0
Previously, it assumed that the transition started from an overlay -
either all apps or the widget picker. But this isn't true, because
the transition is also used when transitioning between workspace
states such as from normal to overview. Properly handling this case is
critical for the workspace to correctly manage the transition. For
instance, it wasn't setting mIsSwitchingState to true, causing issues
such as invisible overview panels in landscape mode.
Change-Id: I9c06a345233d366669972359c58c3427a518e2b9
> Using ViewTreeObserver to listen for onDraw instead of overriding onDraw in workspace
> Loader passes the list of deferrerd runnables to launcher
Change-Id: Ie4877f746c96e9497396de8089f00f70bf867e17
It is a bit clunky and doesn't have the App Info drag bar at the
bottom yet, but it is a start.
Also removed page hints because they are no longer used.
Change-Id: I1f8f82d33e6694cab1f1c762e78852ac0d40ab33
- Also fixing case where the all apps button to search for more apps
was not focusable
Bug: 20639227
Change-Id: Ie4d9092e654d3cafc0eb346b3bb744ec3e295e92
- Routing the various places where we call through to delete from
LauncherModel through Launcher, which will delegate the removal
of the icon from the workspace, and properly handle the removal
of all items and their contents from the db.
Bug: 23944119
Change-Id: I022fe2b3e79da16b5af87505c4362490b8422686
Previously the search began with the page that the user
long-pressed to enter the overview, even if they then free-
scrolled to another page before selecting "Widgets."
Change-Id: Ie286f6864c78b573c05dd9d02c1346e17db711a6
The search for this page starts at the current one and
continues to the right (on LTR) until a page is found that
can accomodate the widget, taking possible resizing and
reordering into account.
Bug: 11338870
Change-Id: I2e9a310eb8f74024dca9150f55a525e1309c2f07
* commit 'c74e41973a74aa416e16aeadaa2f491153da26bc':
Restoring provider behavior for reloading app on old devices > For older devices, launcher will only reload in case of inserts with specific query parameters > For older devices, launcehr will notify content observers of any internal inserts > Chaning TAG for Launcher provider as max logging tag is only 23 characters
* commit 'c74e41973a74aa416e16aeadaa2f491153da26bc':
Restoring provider behavior for reloading app on old devices > For older devices, launcher will only reload in case of inserts with specific query parameters > For older devices, launcehr will notify content observers of any internal inserts > Chaning TAG for Launcher provider as max logging tag is only 23 characters
> For older devices, launcher will only reload in case of inserts with specific query parameters
> For older devices, launcehr will notify content observers of any internal inserts
> Chaning TAG for Launcher provider as max logging tag is only 23 characters
Bug: 23821706
Change-Id: I32891387612d967c41ddae848c43dc4b1de1b0e9
Previously there was a workaround to ensure that adjacent panels were visible
while in the overview or spring-loaded states, but it incorrectly kept only
those original pages visible even while the user scrolled to other pages. So now
we only use the workaround when first entering the overview or spring-loaded
states, and then fall back to the default getVisiblePages() implementation in
PageView when in free scoll mode.
Bug: 23766408
Change-Id: I692ec00b9cd6d7889c374aee41b85abd0a5d8d3c
Since power save mode (introduced in Lollipop, also known as battery saver)
disables animations, the ReorderPreviewAnimation looks bad - instead of
displaced folders subtly and smoothly moving up and down, they violently jump
between up and down positions in rapid succession. Setting the animation to not
repeat in this case avoids this issue.
Bug: 23675090
Change-Id: I8149610af75e7023dca28a942b3447228083cd33
(cherry picked from commit 9e0702f4af)