The supported way to customize Launcher and add a "-1 page" is by
using LauncherOverlays. Custom content screen is no longer supported.
Change-Id: I3f8a2734c287d1a69ae0c038ec1de1d45fa1b464
- Just skip the animation if we are animating to the same wallpaper
offset (which is the case when we are adding from all apps)
Bug: 28587903
Change-Id: Ib7b1828c1b099a665d68c22cb33ee62693f33f35
- When launcher starts up, onCreate() triggers the launcher model loader
to start, which calls bindScreens() to add the workspace pages.
However, layout does not happen until the device is unlocked, which
means that even though the default screen index and children are there
the page scrolls are calculated incorrectly, and even in RTL, the
page scroll for the 0th screen is zero (it should be at the right
most edge of the workspace). This CL works around this by deferring
until the first layout after bindScreens() to unlock the wallpaper
offset from its default bounds. The workaround is only applied when
the launcher activity is first created.
Bug: 28795125
Change-Id: I33da0d7f934f5337d26e69f068f579a32897a837
- Ensure that we map the scroll offsets to the full wallpaper offset
range
- Default to either edge of the wallpaper (depending on RTL) to match
the default system wallpaper behavior (ag/1265418)
Bug: 28795125
Bug: 29398681
Change-Id: I36c316095057912d2dda0beb43bd1e6aaeac3fdc
Pierre Barbier de Reuille
Sunny Goyal
Winson