- Without this, the following type of issues manifest: if shade is
pulled down when folded and then the device is unfolded, the taskbars
are recreated but on the connected display the taskbar is stashed
because on unfolding the shade remains pulled down and because we
reused share state the taskbar on connected display remains stashed.
Test: m
Flag: com.android.window.flags.enable_taskbar_connected_displays
Bug: 414767865
Change-Id: I7579f70edf342f5f34e7884a26c2decb512e3143
BgDataModel holds a mutable handle of the data, which ensures that all edits go through this class and there is a single place to keep the repository updated
Bug: 390572144
Test: Updated existing model tests
Flag: EXEMPT refactor
Change-Id: I991b707dd21801d1abd00510f676549947285012
- Ignore blur changes smaller than 1dp unless going to/from 0.
- Don't apply depth animation during app launch from blurred
All Apps.
- Use DepthController directly rather than creating a new one
for other app launch animaitons. Avoids extraneous memory and
performance overhead.
Bug: 411292920
Bug: 410973453
Bug: 408284263
Test: forrest perf tests
Flag: com.android.launcher3.all_apps_blur
Change-Id: Id5c8e71b19ebb8f1c1b82f8c5c76785e001017af
Added SYSUI_STATE_IME_VISIBLE flag to MASK_HIDE_HANDLE_VIEW to hide the
bubble bar stash handle view. Also update alpha to 1 for the stash
handle view when visibility is updated to VISIBLE.
Fixes: 403363673
Flag: com.android.wm.shell.enable_bubble_bar
Test: Manual. Have stashed bubble bar and multiple system languages.
Go to settings (or ane other apps that has input fields). Click on
search to trigger keyboard pop up. Observe that stash handle is hidden.
Collapse the keyboard and observe that stash handle is shown again.
Change-Id: I5c8518cf02cc784243f9f55a95022279b2608760
Use task offsets to determine which spring drives which, as columns should move in unison.
Fix: 403234864
Test: Manual
Flag: com.android.launcher3.enable_expressive_dismiss_task_motion
Change-Id: I48f7f2a7fcfbd2850d371b4bc7eed3296a2a650a
Bug: 408028262
Test: See https://b.corp.google.com/issues/407711750#comment3 for a screen recording showing this works well.
Flag: com.android.launcher3.enable_launcher_visual_refresh
Change-Id: I76d5551da28fabf7548e15781680b240daaa2e36
During quick switch we will always need to have background Transparent for consistency.
Previous implementation of Quick switch state was inconsistent. Hence making quick switch state return always transparent.
Bug: 416217645
Test: Quick switch between apps.
Flag: com.android.launcher3.enable_overview_background_wallpaper_blur
Change-Id: I561dd6509bbadbbdc751308740d8152bcb0c4032
Also changed TouchInteractionService gestureNavMode to be per-display
Bug: 415269541
Flag: EXEMPT bugfix
Test: local + presubmit
Change-Id: I0da978e6fcb29f743b41f1c75c6d0efd8e7231a8
This cl simply reuses logic of setting the default taksbar window size upon rotation of device.
Test: Manual
Bug: 411587814
Flag: EXEMPT bugfix
Change-Id: I65149425b8d03240c3c4ab09ec0ec82be6b40c8f
testOverviewForTablet was ignored for over a year and other tests cover
most of the test cases of the original test so removing
Add separate tests for grid re-balancing
Fix: 315376057
Flag: EXEMPT. Test
Test: TaplTestsQuickstep
Change-Id: I33016ccdb68b1c2039c626a6d32821de71509506
This requires a decent sized refactor. Namely, rather than relying on
mCurrentPosition we need to rely more upon mLastPosition and
mFinalPosition for increasing and decreasing dot size. We also need to
delay the animation start if we are mega-moving to have the desired
delayed dot change effect.
Bug: 407711750
Test: Verified this works locally. Please see the bug for a screenrecording that shows this correct behavior working.
Flag: com.android.launcher3.enable_launcher_visual_refresh
Change-Id: I83ef113c17f2197e3c02e85f44cf3f05947d2adb
Keep these file in synch with the nudge proto definition in //depot/google3/java/com/google/android/desktop/growth/proto.
Bug: 416054612
Test: EXEMPT add in the follow up CL
Flag: EXEMPT add separately
Change-Id: I5fe6ae7b3cb285bd1c07fd4ff54b273799ec0d98
- Use supplied TaskbarActivityContext to evaluate padding in dp instead
of Resources.getSystem that doesn't seem to provide accurate
measurement when launcher is initialising.
Fix: 414343355
Test: m
Flag: EXEMPT minor refactor
Change-Id: Ia64a7280ba60534fc949269c5886e9b32a917e03
In TaskViewUtils, the StateManager#movetoRestState method is invoked after the recents animation finishes and before the launcher state is reapplied. The issue leading to a phantom transition is that moveToRestState initiates an animation due to RecentsWindowManager#shouldAnimateStateChange always returns true.
Connected display overview is similar to 3P recents. And thus, we follow RecentsActivity#shouldAnimateStateChange to always return false.
Test: manually click on a overview tile in the connected display. No phantom animation is observed after switching to the app.
Flag: com.android.launcher3.enable_overview_on_connected_displays
Bug: 415245440
Change-Id: I3c9600cae6ce9058749365734f433f5e3cdb9445