| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Original qt-future-dev change was ag/10601877.
The change needed to be in UiFactory, not RecentsUiFactory.
Fixes: 146593239
Test: Installed NexusLauncherDebug on a QD4A build and
tried the repo steps. Also built other launcher variants.
Merged-In: Ib9c85de2f83f99d1ef53fb17fde5d0b3c514849a
Change-Id: I802e2b0069a19ca62a08325bb6d0de5275c43c9b
|
|
|
|
|
|
|
|
|
|
| |
Add wallpaper changed broadcast receiver to BaseDragLayer, which
checks if the new wallpaper is blacklisted and relays that to
remove the scrims.
Bug: 150144115
Change-Id: I55b7b98fdd419cd76532492461a872367efed67b
(cherry picked from commit d6f917f1824ed97e6f9a225fe1600a8162922d31)
|
|
|
|
|
|
| |
Test: Tested locally
BUG: 150688842
Change-Id: Ifa96bd01363de47cf1d8cdce34d81d525c8c2c04
|
|
|
|
|
|
|
|
|
|
| |
Test: Used Facebook chatheads (not system bubble).
Before the change, Home gesture didn't work. After
the change, it does work :)
Bug: 146593239
Merged-In: Ib9c85de2f83f99d1ef53fb17fde5d0b3c514849a
Change-Id: I19d91aaed19ccaec68478e364ce6b80049d49a98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
All caused by running the transform progress from 0 to 1 instead of
starting at whatever the progress was before ending the gesture, e.g.:
- When swiping to home without animating into an icon, the corner radius
was set back to the window corner radius.
- Before this change, the clip didn't update throughout the animation,
making the window slightly bigger than the floating icon view; after
this change, the clip jumped to show the insets again before clipping
back down during the home animation.
Partial backport of ag/Ie48f4b665a5bf3cbef76bdf7f043febe99fb84a0
Bug: 150680980
Change-Id: Ida65097f0ef7d2e11d48b84ecdd353ef89078015
|
|\
| |
| |
| |
| |
| |
| |
| | |
Test: manual, presubmit on the source branch
http://x20/teams/android-launcher/merge/ub-launcher3-qt-future-dev_6048032.html
Change-Id: I74059dbc75a8530884f8b4f67917b83c75f32d14
Merged-In: Ieee38cc301364f96cf252b2387142b0aa1b75317
|
| |\
| | |
| | |
| | | |
ub-launcher3-qt-future-dev
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When flinging up and to the right, we previously always returned
home. Now, if the right velocity is stronger, we quick switch.
Bug: 126596417
Change-Id: I14fa0584399bb90f2e07e0b296fc5932d8224fbf
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- The bug is caused by cancelling of the RectFSpringAnim before the
StaggeredWorkspaceAnim has started.
- Instead of having logic in StaggeredWorkspaceAnim control the visibility
of the icon, we instead maintain all the visibility within the
FloatingIconView class itself.
Bug: 142120338
Change-Id: I94f3a066d395f9c3b97dc6ee9fc836e9401650a5
Merged-In: I082291ca9b288f57701cc00d61a9b3a84da8b084
|
| |\
| | |
| | |
| | | |
ub-launcher3-qt-future-dev
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We were previously offsetting the launcher animation progress based
on when we got onGestureStart, which meant it would lag behind if
onGestureStart came late. Now that we track the window instead of
the launcher shelf, and we don't show the launcher animation right
away in fully gestural mode anyway, we should remove this to ensure
the launcher part of the animation always lines up with the app
window.
We also reapply state whenever predictions are enabled, e.g. when
launcher starts after being force stopped, and previously this was
canceling the existing state animation. We don't want to do that
because predictions can be enabled at any point on a cold start,
and cancelling the existing state animation means that RecentsView
shows up in fullscreen and not attached to the app window for the
duration of the gesture.
Bug: 144454486
Change-Id: I65a2c71c9acd2f5345941ea2cff7d32c04b7be3f
Merged-In: I65a2c71c9acd2f5345941ea2cff7d32c04b7be3f
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- Add NoButtonQuickSwitchTouchController which uses
BothAxesSwipeDetector to track horizontal and vertical motion.
- Initially, we only detect swipe left to right to quick switch
(like before), but then we allow swipe up to either go to
overview (if you hold) or back home (if you don't hold).
- xDisplacement transitions non-overview components out (e.g. shelf
and workspace), and translates overview in.
- yDisplacement translates overview up and scales it down
Bug: 126596417
Change-Id: Id679ad84c08246e205c667a78ed5df00d7276258
Merged-In: Id679ad84c08246e205c667a78ed5df00d7276258
|
| | |
| | |
| | |
| | |
| | |
| | | |
Bug: 126596417
Change-Id: I5ba501b04b3eaf12a20ba1312ef362f9734761c3
Merged-In: I5ba501b04b3eaf12a20ba1312ef362f9734761c3
|
|\| |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Test: manual, presubmit on the source branch
http://x20/teams/android-launcher/merge/ub-launcher3-qt-future-dev_6018744.htmlMerge commit '9353b00616ac688d2df6b9f8513c4895bb4119d7' into merge_ub-launcher3-qt-future-dev_6018744
Change-Id: Ie6235a262b7bba0aa9f2a2962a7aa499a0a2cb53
Merged-In: I8a1e20d0b175f03a1a05c81749f07ab5314e872a
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Test:
1. . build/envsetup.sh && tapas NexusLauncher
2. ccdebug && cclogcat
3. launch from workspace any app that is also in predicted apps
4. verify in terminal it has correct predicted_rank
Bug: 143855018
Change-Id: I07a62f07057537a6c09384cf944bbc5aa5888d22
Merged-In: I07a62f07057537a6c09384cf944bbc5aa5888d22
|
| | |
| | |
| | |
| | |
| | | |
Bug: 141265005
Change-Id: I3b11146881af334508f553e4ca3a36b9291511d9
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Launcher.
Previously it was using OtherActivityInputConsumer, which got things in a
pretty weird state (e.g. most recent app would appear in the center as if
it was the active app when you started Quick Switching, etc.).
By default (toggleable by a feature flag), OverviewWithoutFocusInputConsumer
is used because Assistant doesn't seem to respect the CLOSE_SYSTEM_DIALOGS
broadcast, at least in half-shelf mode. In this case, the Home intent is
sent on swipe up, or you can dismiss it with the back gesture or by tapping
above the half shelf.
The new feature flag ASSISTANT_GIVES_LAUNCHER_FOCUS routes touches through
OverviewInputConsumer. As opposed to OverviewWithoutFocusInputConsumer,
this allows Quick Step to work while Assistant is running. Additional logic
is added to dismiss the Assistant when appropriate. Note that the dismissal
happens atomically, so it's not completely fluid with the other animations.
As mentioned above, this is disabled by default because Assistant doesn't
currently respect CLOSE_SYSTEM_DIALOGS.
Demo with the flag enabled (and Assistant respecting CLOSE_SYSTEM_DIALOGS):
https://drive.google.com/open?id=1W5jGpn_TEC-KjrYwQtaBT3pzxG_5tC4W
Bug: 139661510
Change-Id: I261653118aff289b329ec2a7ca6e52f100f7835a
Merged-In: I261653118aff289b329ec2a7ca6e52f100f7835a
|
| | |
| | |
| | |
| | |
| | |
| | | |
Bug: 141886704
Change-Id: I0178a52088dd4150d7ba054983697ea63a00d9a8
Merged-In: I0178a52088dd4150d7ba054983697ea63a00d9a8
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Existing clients now use the SingleAxisSwipeDetector subclass. A
followup CL will add BothAxesSwipeDetector, whose first client will be
the quick switch from home controller.
Bug: 126596417
Change-Id: I54c71088cfe99ff28cdc719a1eb7a7d06ac95d2d
Merged-In: I54c71088cfe99ff28cdc719a1eb7a7d06ac95d2d
|
| |\
| | |
| | |
| | | |
ub-launcher3-qt-future-dev
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This makes the transition smoother, since
the Assistant goes away at the end of it.
Note this only applies to the transition
while an app other than Launcher is live.
Before: https://drive.google.com/open?id=18SOWTtTUzt19TReAYnofQLIShJ2I-odP
After: https://drive.google.com/open?id=1hqsikXSlCnSvNg0ZQYHxP-OIbS5yt9aW
Bug: 136282913
Change-Id: Ia53c2407c82725c776f27b0d6e80a34554b4a303
Merged-In: Ia53c2407c82725c776f27b0d6e80a34554b4a303
Tested: Manually
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This adds another card in the Recents Overview space which can show various items.
Change-Id: Ifc36639ece8aa6b554bdbd3256f4195b1b220d68
Merged-In: Ifc36639ece8aa6b554bdbd3256f4195b1b220d68
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- Don't set current page to running task when applying load plan,
if we are already settling on a new task to launch.
- When starting a new task, finish to the running app if that's
the task being started (should not happen with above change)
- When disabling free scroll mode, don't snap to a page if we're
already on it. This was setting mNextPage so the first check
was falsing.
Bug: 142068081
Change-Id: I5b392d9726a81c51718d2f94eee6cd4f78b61f69
|
| |\ \
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | | |
ub-launcher3-qt-future-dev
Bug: None
Test: I solemnly swear I tested this conflict resolution.
Change-Id: I9a3b0f67ee874b5ec4ad67f41a46ec7876d19082
Merged-in: I9a3b0f67ee874b5ec4ad67f41a46ec7876d19082
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Not doing this seems to have caused flakes.
Bug: 141770616
Change-Id: Ia9caf20e4a2d93298adf4249ca815ad79bced802
Merged-in: Ia9caf20e4a2d93298adf4249ca815ad79bced802
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Previously, predictions faded in quickly but then all apps faded in
linerally over entire rest of the transition. Now, all apps fades in
quickly after reaching the overview threshold where predictions are
opaque.
Also implemented the reverse, so that predictions/all apps content
remain opaque when returning home until reaching the overview threshold
near the bottom, where they fade out as quickly as they faded in.
We do this for 3-button mode as well.
Bug: 141986013
Change-Id: Ia35ab3ac9714e89f754293445a7839e15da5313d
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Once the inputProxy (OverviewInputConsumer) was enabled, it was never
disabled. And while it was enabled, touches above the nav bar would go
through to launcher, allowing you to scroll RecentsView (for example)
during quick switch transitions. This breaks some assumptions, since
it doesn't go through our normal shared swipe state logic that cancels
the animation, updates the new end target (e.g. NEW_TASK vs LAST_TASK),
etc. Thus, if you tried returning to LAST_TASK via this route, we would
end up starting it as a new activity instead of resuming the existing
one, causing a flicker (I guess because that TaskView is hidden).
Test:
- Swipe up from task A to home (to enable input proxy)
- Open A
- Swipe to B, and during transition scroll back to A from the center of
the screen
Before, this caused a flicker, now the last scroll is ignored.
TODO: we should increase the nav region during quick switch to make it
easier to continue scrolling
Bug: 136829198
Bug: 138620399
Change-Id: I5ffb53743b728e1909066c5dd18cc9308aff2c7e
|
| |\ \
| | | |
| | | |
| | | | |
TaskView." into ub-launcher3-qt-future-dev
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Bug: 139828243
Change-Id: Idbefc11ef32619dd5eaaa5552088859eb2304e1e
Merged-In: Idbefc11ef32619dd5eaaa5552088859eb2304e1e
|
| |\ \ \
| | |/ /
| |/| /
| | |/
| | |
| | | |
am: b72cd2629c
Change-Id: Id28e20b5fe23c6f6501f3c7a38305f0a306b287a
|
| | |
| | |
| | |
| | |
| | | |
Bug: 141275518
Change-Id: I171361d4f797f587b404eed07108224d8ab844f8
|
| |\ \
| | | |
| | | |
| | | | |
ub-launcher3-qt-future-dev
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Couple of benefits here:
- Doesn't rely on having a measured TaskView, since it already knows how
to calculate the task size
- Code can be shared (planning to use this for quick switch from home)
Bug:
Change-Id: I517a78506ac95fcc37d9225a074427941d691903
|
| |\ \ \
| | | |/
| | |/|
| | | |
| | | |
| | | |
| | | |
| | | | |
ub-launcher3-qt-qpr1-dev
am: 76aadac4e4
Change-Id: I5099741d3502584f7d501d74897944edc3339977
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Bug: 139941530
Bug: 140311911
Change-Id: Idf4c013373e627db92aa96f9207e25336ee039f8
|
| |\| |
| | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | | |
ub-launcher3-qt-future-dev
Bug: None
Test: I solemnly swear I tested this conflict resolution.
Change-Id: I41247ff46308b72158731e4a47466533d42e67c6
|
| | |\
| | | |
| | | |
| | | | |
ub-launcher3-qt-qpr1-dev
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This can happen in LockTask mode, after enabling Overview. In that case,
you are locked to the current task, but are allowed to go to overview
but no tasks are shown there.
Bug: 139917483
Change-Id: I2180cc5e72c343977ea53cc02907ed8dac0f8bc6
Merged-In: I2180cc5e72c343977ea53cc02907ed8dac0f8bc6
|
| |\| |
| | | |
| | | |
| | | |
| | | |
| | | | |
am: 9f6cde1443
Change-Id: I31ce596847aa1506cefbde711ae6ad6f3e3b777e
|
| | |/
| | |
| | |
| | |
| | | |
Bug: 141275518
Change-Id: I95544a55ef13002f696a82e52d54ffb6251d0e39
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
all connected plugins.
Listener for this plugin is added in PredictionAppTracker which receives
all app events.
Change-Id: Iec53d20272f6a587f78e3d84666efa4f02cf6962
(cherry picked from commit ae084dafd936a0544230cc6984b5aa45ec7ff935)
|
| |\|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
ub-launcher3-qt-qpr1-dev
am: 24fb1526e2
Change-Id: I59bf92b05d45c31705166e1211cf02ccbc348383
|
| | |
| | |
| | |
| | |
| | | |
Bug: 124967099
Change-Id: I7bf576759b3fa4f6ca617fbbd660541c12fd09ac
|
| |\ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
predictions" into ub-launcher3-qt-qpr1-dev
am: fc520edbc6
Change-Id: I8e5b43a582bd243e21f02b5a83b931f4f277eb95
|
| |\ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
precomputed values" into ub-launcher3-qt-qpr1-dev
am: 791dd73217
Change-Id: I1ecde4721df9895b0fb215f36a43d8cb85a392ef
|
| | | | |
| | | | |
| | | | |
| | | | | |
Change-Id: I0bc28ef670a1dad9a3912ca5360c9bab18afd4b2
|
| |\ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
* changes:
Defer listening on widget host until after the state transition ends
Migrate to using DefaultDisplay
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
- Remove extra binder calls to get the default display
Bug: 140633033
Change-Id: I532645deac101a6065d90484b87a67b67aa717f5
|
| |\ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
ub-launcher3-qt-qpr1-dev
am: 329cc8c53f
Change-Id: Ib1e4040010cf3919163e24971d2a368664bec1db
|
| |\ \ \ \ \ \
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
into ub-launcher3-qt-qpr1-dev
am: d785fc289c
Change-Id: I69738f5d9c1f77195f2f82f963958d3cc741e9af
|