> This allows us to use all the goodness of material theme
> Cursor in folder edit text is no longer 1px wide
Change-Id: I705f5472ff71969ae45747dd127a8ba5253df44d
- If you queue up two SearchBarDropTarget state transitions one right after
another, the second animation will skip (since the values haven't started
animating yet) and the first animation will complete instead, leaving the
visibility of the search and drop target bars at odds with the current
bar state.
- Instead, we should cancel all existing animators first, such that if we
are already in the final state, no animations will run, and the correct
bars will be visibile.
Bug: 23201830
Change-Id: I1f8e802821ef2b4904a3efa7edbea6ae615479b9
- Issue: The fast scroller currently does not follow the touch input
because fundamentally, the fixed scrollbar height and the mapping
of the scroll space to the scrollbar space is fundamentally incompatible.
- This CL changes the fast scroller to allow it to detach when the user
fast-scrolls, then re-attaches after the user scrolls the screen and
the current scroll position for the scrollbar picks up the thumb position.
- Since the scroll position and the fast scroller thumb is now detached,
we can change the distribution of the fast scroll letters to make it
independent of the rows for each section and instead uniformly distribute
it along the scrollbar, which allows for more stability.
- There are edge cases where this fails, especially when there are few
apps, which we can investigate further.
Bug: 20035978
Change-Id: I8322f862107e6f330deff692885233706564bffd
- Since move to default screen starts the scroller immediately, any delays in
handling onNewIntent and onHomeIntent in the callbacks will cause the scroller
to skip frames the next time it updates. This change will defer updating the
page to the default screen until after onNewIntent is called back (and all its
posted runnables).
Bug: 22929080
Change-Id: Ibab6106938721702d4da23faaca99039861e10dc
> Renaming Lmp to Lollipop
> Lollipop_MR1 instead of directly using 22
> Using M APIs directly instead of reflection
Change-Id: I10a307f46e3be15b3299f549a2fd7e0e215a6a1b
This fixes perhaps an old bug.
If we started an accessible drag for an only item on a page,
then uninstalled the app while dragging, the page was removed
without unsetting its accessibility delegate. Later, the system asks
the delegate to do something, but the drag is over, and some pointers
are null, so everything crashes.
Fixing this.
Bug: 22028725
Change-Id: I85adcd42ae896603634994e20a7790792f7e84b1
(cherry picked from commit de1e67c388)
- There was an issue with the previous logic where the test of whether
the search bounds changed would always be false if valid search bounds
were given. This in conjunction with the fact that the padding was
changed to only take the bounds left/right into account, meant that
the container bounds would not be updated if the search bar bounds
shifted via the insets.
Bug: 22918919
Change-Id: Ia810ddc7a56eae4afc0c7cd558fa6dc9e8e7a95b
- We used to rely on the state transition to inflate the search
widget after the permission to bind widgets was granted, which
is fragile. Now we try and inflate the search widget after
user grants the permission if necessary.
Bug: 22515084
Bug: 22980143
Change-Id: Id111d263bc8a864e0fa652cfd0e07e66ec690fe7
- This refactoring ensures that LauncherStateTransition does not
do its own animation on the QSB, and that all animations to the
SearchDropTargetBar go through its own animators.
Bug: 22515084
Change-Id: Ia7d13c44d861eac7517076b52a9651a90911ed0a
Sunny Goyal
Winson
Geoff Mendal
Vadim Tryshev
Adam Cohen