- Scale down current task and translate it to the left
- Translate previous task in from the left
- This is a toggle; quick switch again returns to the first task
Currently this is implemented by repurposing onQuickScrub(progress) to update the positions
of the first two pages. This makes tracking velocity a bit difficult; if we want to go down
this path in the long run we should probably track velocity properly on MotionEvents.
Change-Id: I4445b5f08b6e88e71cbb5e30b1f1d45c5f1edc68
Consider these steps:
- Swipe up for recents
- Scroll over several cards
- Swipe up for all apps
- Press home
Before this change, there was a delay as recents scrolled back to
the workspace card before going home, even though it wasn't visible.
Change-Id: I1c0edc8e02d1d1d236f47882695903e33e6b09ae
-> This change provides integration for widgets provided by
the launcher package which can run arbitrary code.
Change-Id: I6052da5c4afed7ee72e3b44d045b9c46f2d84c42
Instead of fitting system windows as before, DragLayer now
lays out under the system windows.
DragLayer will simply add the system window insets to each
child's layout margins by default. e.g. for Hotseat, Page
Indicators, QSB, Search Overlay.
Children that want to use the full viewport can declare so
by implementing a new Insettable interface. System window
insets will be passed to Insettable#setInsets(insets) and
the child can do what it wants with them.
Currently, two of DragLayer's children implement Insettable:
1) Workspace (for the -1 screen).
Full screen pages are given the entire viewport, paged
view offsets modified to end up in the right place now
that the viewport is larger (the full screen height).
Non-full screen pages like the normal icon pages simply
apply the insets to end up in the same place they did
before.
NowClientCardsView uses the full viewport, applying the
insets as padding. Will want to better take advantage
of this new real estate in a future CL.
2) All Apps (AppsCustomizeTabHost).
Applies the insets as layout margin one level down, so that
the bar area is opaque during the transition, but visually
the content lands in the same place.
(Also add db_files to .gitignore to ignore the output of the
db tool)
Bug:10687177
Bug:10652189
Change-Id: I80b25d63884d244fcf704b24dad9497ee0d8b453