Skip to content

GitLab

Switch branch/tag
  1. 12 May, 2016 2 commits
  3. 11 May, 2016 3 commits
  5. 10 May, 2016 3 commits
    • Hyunyoung Song's avatar
      Merge "Fixing bug where the widget background enters into a focused state if a... · 0fb31cf7
      Hyunyoung Song authored 
      Merge "Fixing bug where the widget background enters into a focused state if a child calls requestFocus in xml" into ub-launcher3-burnaby-nyc
      0fb31cf7
    • Yohei Yukawa's avatar
      Enable selection action mode for Android M+. · fe1de383
      Yohei Yukawa authored 
      Since I62963d225e6ea5d2ec9d8ebc8a6d73099f5d6c7f, we have disabled
selection action mode in the folder-name editing mode on Launcher,
mainly because it messed up the view on phones.  However that is no
longer the case in Android M and later, where floating action mode
is available.

With this CL, we start relying on the default floating action mode
in Android M and later.

Bug: 22210697
Bug: 28526978
Change-Id: Ie19e7844194acd86cdb013254a1923f0b1d78e11
(cherry picked from commit 1bd9a430)
      fe1de383
    • Hyunyoung Song's avatar
      Fix home button returning to now screen issue · d419681a
      Hyunyoung Song authored 
      b/27978139

Background: onSaveInstanceState assumes that state of the launcher
is being stored after screen is all binded. However, due to ActivityStack
bug in nyc, onCreate is called twice when the device is rotated while
the Launcher is in the background. The first onCreate fails because
our AndroidManifest is setup with nosensor field and hence doesn't support
Landscape. During this first onCreate, screen is not correctly bound
and incomplete workspace state is saved. This results in the second onCreate
to load wrong screen id.

Fix: While the workspace is still being bound, mSaveState is not reset,
which has the correct values. SaveInstance should use this state
instead of incomplete workspace state.

Change-Id: I5b80f584e55769b2a8ffa292f5daa4705c20086d
      d419681a
  7. 09 May, 2016 2 commits
  9. 06 May, 2016 2 commits
  11. 04 May, 2016 1 commit
    • Tony Wickham's avatar
      Return 1f in Log(Ac/De)celerateInterpolators on a 1f input. · 8dd24099
      Tony Wickham authored 
      In battery saver mode, animations skip directly to the final values.
For LogDecelerateInterpolator, however, an input of 1f outputs an
interpolated 0.99999994. This meant that the FirstFrameAnimatorHelper
didn't realize that this was the last frame, and messed things up.
Since any interpolator should return 1 on an input of 1, we just
short-circuit in that case for the log interpolators.

Bug: 25666809
Change-Id: I60527e3758cea383fbcf50acb95460a7bd9ab43c
      8dd24099
  13. 28 Apr, 2016 1 commit
  15. 27 Apr, 2016 2 commits
  17. 21 Apr, 2016 1 commit
  19. 20 Apr, 2016 2 commits
  21. 19 Apr, 2016 1 commit
  23. 18 Apr, 2016 1 commit
  25. 13 Apr, 2016 3 commits
  27. 12 Apr, 2016 7 commits
  29. 11 Apr, 2016 8 commits
  31. 08 Apr, 2016 1 commit