| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Bug: 28054048
Change-Id: Ic22e7e717c3ead52dd6fb7495c37be3837e11030
|
|
|
|
| |
Change-Id: I3361383fe19faa64d862bbf879edb8c09937dc6f
|
|
|
|
|
|
| |
This reverts commit debf81470dcb42b971d52d582d23a0d1da63d4a8.
Change-Id: Ib5b60c21be2d112c6c6e453168cb5bf01a7bd971
|
|
|
|
|
| |
Bug: 28054048
Change-Id: I081db915445b60f96607d4a0c30ffc8ab476fe24
|
|
|
|
|
| |
Bug: 27135377
Change-Id: I470955ed082a45ae7dc5f8fdd1f3decb2b573dbc
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There are 3 classes coordinating the gesture: PinchToOverviewListener,
PinchThresholdManager, and PinchAnimationManager.
- PTOL listens for the pinch gesture on DragLayer.
- When a pinch is detected, the PTOL keeps track of the interpolated
progress and passes it along to both the PTM and PAM.
- The PTM uses the progress to determine whether a new threshold has
been passed, and tells the PAM to animate it if so.
- The PAM uses the progress to animate things like workspace scale
throughout the pinch.
- If the pinch ends early, the PTOL uses the last passed threshold to
determine whether to animate to workspace or overview, and tells
PAM to perform the animation at the same velocity as the pinch.
Bug: 24414635
Change-Id: I9e53706c705f8b2982409bf7c223d8d0e9618bf0
|
|\
| |
| |
| | |
ub-launcher3-calgary
|
| |
| |
| |
| | |
Change-Id: Ie11b92cd59c90e71b9b58eeede742ef0c5b28380
|
|/
|
|
| |
Change-Id: Ia46c4ef3db8a3ae4fa615625b7b983d7e461c797
|
|
|
|
|
|
|
| |
> Sending unboundX to the overlay which is the total untranslated X and not just deltaX from last frame
> Handling overlay callback and translating workspace accordingly
Change-Id: I3bd8d9efac738e9ce131758f0e5ff1b9c1d6a8fc
|
|
|
|
|
|
|
| |
-> Created com.android.launcher3.folder package to house most folder-related files
(aside from the FolderInfo) which is more related to the model than the UI.
Change-Id: I767063e1e4c775c01a799a3bede30cd94ac48ade
|
|
|
|
|
|
| |
These will be visible in hierarchy viewer
Change-Id: I940724a7f61d67b8502d77be203a94875bc92668
|
|\
| |
| |
| | |
Change-Id: Id48bf33912bf927121356a08b8501ee0070bfdc7
|
| |
| |
| |
| |
| |
| |
| | |
dispatchDraw was calling getVisiblePages which in turn calls
getDescendantCoordRelativeToParent and created multiple new abjects
Change-Id: I401fec076183979d30dfdbbdc02a57bd79f3886d
|
|\|
| |
| |
| |
| |
| |
| | |
am: ecdc24f6f6
* commit 'ecdc24f6f667319db56a16dd7d1efda16dfe662e':
Fixing custom content screen not aligned properly in landscape
|
| |
| |
| |
| |
| | |
Bug: 26413100
Change-Id: I1a111c9d2b0dfdfbc3cbd566e5784a1ed2bb6719
|
| |
| |
| |
| |
| | |
Bug: 24900496
Change-Id: Ie1318b82b497957b99603b11ec338dd50d51b962
|
|\|
| |
| |
| |
| |
| |
| |
| |
| | |
focused" into ub-launcher3-burnaby-polish
am: 093a58cc77
* commit '093a58cc776be2a3cd5aed9d14df9c78a35af052':
Keeping the focus indicator on the widget view, while a child is focused
|
| |\
| | |
| | |
| | | |
focused" into ub-launcher3-burnaby-polish
|
| | |
| | |
| | |
| | |
| | | |
Bug: 25199581
Change-Id: Ie08d1438ae0c1b5d4fcaa4d642508c1b9db0f5d4
|
|\| |
| | |
| | |
| | |
| | |
| | |
| | | |
am: 9326461652
* commit '9326461652c36c2ddd888d1452cf7f075a391868':
Adding margin to Drag layer instead of checking for right insets at every place
|
| |/
| |
| |
| |
| | |
Bug: 25692432
Change-Id: I853f41a17c54b30b7772b9fd8556d9465de84752
|
|\|
| |
| |
| |
| |
| |
| | |
am: 04e2c9ef56
* commit '04e2c9ef5663262fc9dd08ffc4b59fe305a017f3':
Stop clearing focus when snapping to a new workspace page.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Clearing the focus was causing the first child in the new page to
immediately take focus, which caused FocusIndicatorView jank when
using a keyboard.
Bug: 25256728
Change-Id: I5ab31ebc3fe370d7ac9e9792b30dab3467023738
|
|\|
| |
| |
| |
| |
| |
| | |
opaque" into ub-launcher3-burnaby-polish
* commit '21d89fbf8c444c64a4c85d25a25bbe3b79719de9':
Fixing overscroll effect when the navigation bar is opaque
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The navigation bar is opaque on mobile devices in landscape mode.
Launcher should ignore the right insets and draw the edge effect appropriately.
Also draw the black bar under the navigation bar, just in case we assume it
to be opaque, but it was not actually opaque.
Bug: 18526657
Change-Id: I1d49dcb82b8a5ee25009bc738cd9b8c0c5c88263
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |
| |
| |
| |
| |
| | |
with different locales
Change-Id: I9639bb11197e656c5cdd3a4d63f913edcc0987cb
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
|\|
| |
| |
| | |
Change-Id: Ia3e845a2e336c846cceefdc2d1e8c6786753f1b1
|
| |
| |
| |
| |
| |
| |
| |
| | |
> Renaming Lmp to Lollipop
> Lollipop_MR1 instead of directly using 22
> Using M APIs directly instead of reflection
Change-Id: I10a307f46e3be15b3299f549a2fd7e0e215a6a1b
|
| |
| |
| |
| |
| |
| |
| | |
> Instead of resizing the rect for dragoutline in onDrow, store the resized rect itself
> Remove unnecessary inverse matrix calculation
Change-Id: If13c3c5aaecba5a1d3a4f5d39199ed82e9662c62
|
| |
| |
| |
| |
| |
| |
| | |
> Using View property instead of strings to avoid extra reflection step
> Using ViewPropertyAnimator when several properties are being animated
Change-Id: I41625643b38b70bac11e2c81d18058ec878d73bd
|
|\|
| |
| |
| |
| | |
* commit 'cb037eee8ca863ad99d9cdbacd6a82759295e5a0':
Fixing overscroll not drawn in rtl
|
| |
| |
| |
| |
| |
| |
| |
| | |
> Using the currect right page index in rtl
> Updating current scroll after max scroll has been calculated. This prevens an extra overscroll when the layout happens for the first time.
Bug: 22358804
Change-Id: If07132701936e06f727211122a3b3e6f8426c07b
|
|/
|
|
| |
Change-Id: I1c7312b46ec95286d8e49d3dee60b1bf4d98dc20
|
|
|
|
|
|
| |
bounds when in transposed layout.
Change-Id: I93be6a003b7d28708697990cfae8c7be96f84676
|
|
|
|
|
| |
Bug: 21335369
Change-Id: I53cc6edfa87334b9326f1dedd90c3e2222beade5
|
|
|
|
|
|
| |
-> thanks adamp@
Change-Id: I36836357f5f194ac69530475b124595174c8b636
|
|
|
|
|
|
|
|
|
|
|
| |
-> When in overview mode, flinging the pages can leave the scroller
running (invisibly) for much additional time, since the scroller
fling bounds far exceed the alloawble scroll bounds (in order to
achieve a hard wall type effect)
-> When this is happening, user couldn't pick up a page for reordering
-> Ended the scroller early in this case to avoid the problem
Change-Id: I8b6f140d9a87bb742e57625e90ca7d76a2158e28
|
|
|
|
|
|
| |
> Make package-private and @Thunk all private methods and constructors accessed from inner classes.
Change-Id: Ie5913860a0c33e48e9bf68f9b5b1699f64c2f174
|
|\
| |
| |
| | |
event." into ub-launcher3-burnaby
|
| |
| |
| |
| | |
Change-Id: Idec0e333a0d3c3a0c232d3e2240f18174e0ea88c
|
|\ \
| | |
| | |
| | | |
vew. The reason for non-scrolling was excluding the pages view from the accessibility hierarchy by marking it as non-important. So, I just removed the code manipulating [non]importance of the PagedView." into ub-launcher3-burnaby
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The reason for non-scrolling was excluding the pages view from the
accessibility hierarchy by marking it as non-important. So, I just
removed the code manipulating [non]importance of the PagedView.
However, this would make the PagesView accessibility-focusable, which is
undesirable. It becomes focusable because it supports long clicks in "normal"
mode. Since it doesn't support accessibility long clicks (i.e. Overview mode is
fetched NOT via accessibility long-click), I just disabled accessibility
long-clickability, which made PageView non-focusable, and it started to behave
correctly.
Bug: 21281859
Change-Id: I7ab01e5f39cb37c456c961199c27458c9bda1c3d
|
| |
| |
| |
| | |
Change-Id: I2d8ac9a92d2da3d6b0f52ff8a6e3683b05663aec
|
|/
|
|
| |
Change-Id: I83c99bb3d3546693200d64e2233957b4c679e7e6
|
|
|
|
| |
Change-Id: Icd17c2956b201ea0b6c6a2a495f567f51987b1ac
|
|\
| |
| |
| | |
AccessibilityEvent.TYPE_VIEW_SCROLLED sent by PagedView. This causes an additional reduntant voice message on scroll (see the bug)." into ub-launcher3-burnaby
|