- This was due to us not re-attaching the thumb to the scrollbar after
we scroll the view to the top explicitly without the user scrolling.
Bug: 23562489
Change-Id: I5932b9b3b9358e23c0ec23aa235644b4f27c43ea
- This would happen when you scroll near the thumb and pass through the
area where the scrollbar was when the gesture started, and this CL
prevents gestures that move beyond a fixed distance from the original
touch position that is not already a fastscroll.
Bug: 23561678
Change-Id: I66226777671456a8919503dae4e92164ee10dd6d
Previous patch Ia4ccc59ca27e560e470122d1b2c6c1eccb4caf9a was
reverted due to a weird behavior around folder name editing
with virtual keyboard.
Also, requestFocus() on doneEditingFolderName() did nothing
because the folder itself didn't get the focus at that point.
This CL addresses these issues:
- no change on the descendant focusability. Folder itself is
focusable before its descendants.
- customize Folder.focusSearch(), so once the folder is focused,
further focus cycle moves among its descendants.
- Folder requests its focus when it appears. Without this,
the first arrow-key after opening a folder by touch moves
the focus to the folder itself, which looks like nothing happened.
Bug: 22562679
Change-Id: I04375bd4cb69d463b9a95bebafa9c60142e95daa
This will enable an easier migration to the new M APIs for identifying
button presses from stylus / other tools.
Bug: 20430722
Change-Id: I41cfa6eff8d76bb83cf1bdaf6623ec1092ed554c
- 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
> Removing utility method for isAttachedToWindow
> Moving logic to calculate cell size from workspace to DeviceProfile
> Replacing some constants with xml resource variables
> Saving the item info using content values for better compatibility with other methods
Change-Id: Idd612633d97a6241cb31148df9466031374bd5a0
- 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
> Showing animation when folder is added
> Not showing animation while cling is visible
> Checking is loader completed from UI thread
> Running bind complete runnables when bind is completed
Bug: 21772992
Bug: 23181585
Change-Id: I50742850da8294a877478ce02b107a026f68b563
This is per an earlier CR comment "we should probably move all this code to its own package (launcher3.dragndrop) in a separate cl".
I'm not moving DragSource because it's referred from gsa code.
Bug: 22609426
Change-Id: Ia7204dab99c0c395c66b77143a2d60411153f5f3
> Only setting desired size on wallpaper change for pre kitkat
> Removing wallpaper change receiver from manifest
> Removing multi-process wallpaper shared prefs for kitkat+
Bug: 23353784
Change-Id: Iba72d32871ee50b75807e2284a73a691bcddc472
- 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
Sunny Goyal
Winson Chung
Jun Mukai
Mady Mellor
Vadim Tryshev