| 45feb95c4a18c5da93da72f448003857b6226082 |
|
11-Feb-2016 |
George Mount <mount@google.com> |
Null check for fade start alpha value.
Bug 27105186
Fade previously hadn't had any values saved over those captured
by Visibility. If a Transition merged two Visibility transitions,
it could avoid calling captureStartValues for the Fade transition.
This change prevents an NPE in that case. The combined transition
won't get the intermediate alpha value, but at least it won't
crash.
Change-Id: I8e5720caafda56b017dfe1cc0b16ebdf246e90c4
/frameworks/base/core/java/android/transition/Fade.java
|
| 5affef077316e73337eb42a098a126b01d20568e |
|
05-Feb-2016 |
George Mount <mount@google.com> |
Fix Fade transition interrupt.
Bug 26963113
When a Fade transition is interrupted and reversed, the
View started the animation from the beginning. This change
captures the previous transitionAlpha and starts the animation
from the previous alpha state.
Change-Id: I801fe9ade6af4cf8446838e231bdc71841668a18
(cherry picked from commit 3cf9fa3db0231d035142c27992818d8f7827ac3e)
/frameworks/base/core/java/android/transition/Fade.java
|
| 28b3ecca86caf8c64eee68dab022d65f5fb0595c |
|
03-Apr-2015 |
George Mount <mount@google.com> |
Reset transitionAlpha when the transition is stopped early.
Bug 19273502
When a transition runs several animators and is interrupted,
some animators may not have been started. Those animators
that haven't been started will not reset their contents
the same as if the animator was canceled. Fade modifies
transitionAlpha and if it is interrupted prior to the
animator starting, the transitionAlpha doesn't get reset.
Change-Id: I8a49b4fbb7151aadc43d7b10e6acbae9578e5cc4
/frameworks/base/core/java/android/transition/Fade.java
|
| dc5bf6a7f0e9d05a1019bb01b406ec1f54cdaa2b |
|
18-Sep-2014 |
George Mount <mount@google.com> |
Default to using hardware layer during fade transition.
Bug 17499864
When hasOverlappingRendering() is true, a layer is used to
to fade views because performance can be much worse then.
When hasOverlappingRendering() is false, the performance
is not hurt and a layer is not used.
Change-Id: If3fb1c23ffc8d0bef85c9d16df6c26ff4bbd49ac
/frameworks/base/core/java/android/transition/Fade.java
|
| ad88e1b1b2c57fa56bde68764b22240d145fa0ef |
|
19-Jul-2014 |
George Mount <mount@google.com> |
API Council: Change docs and constant names.
Bug 16401545
Changed doc for ChangeImageTransform.
Changed IN/OUT to MODE_IN/MODE_OUT.
Changed mode to flag attribute.
Change-Id: Ia2ae9930f9725871c9b1d80b758a3a0808a8f0c6
/frameworks/base/core/java/android/transition/Fade.java
|
| ecd857be3946283ebb4306e2c03ae70f5c5bb152 |
|
19-Jun-2014 |
George Mount <mount@google.com> |
Add curved motion to Transitions.
Bug 15197527
Added two public PathMotions: PatternMotion and ArcMotion.
ArcMotion is the algorithm provided by UX. PatternMotion
provides a mechanism for using a Path as a pattern.
Change-Id: Ie57fd5f4e62269acc1164eced39853a12c52bd77
/frameworks/base/core/java/android/transition/Fade.java
|
| 18ab79967ce8bcde4b1507164ac8186e5135622e |
|
26-Jun-2014 |
George Mount <mount@google.com> |
Add IN/OUT flag for all Visibility transitions.
Bug 15758206
Change-Id: If9b1871117a6808c87adc84ab9215b913ebd2704
/frameworks/base/core/java/android/transition/Fade.java
|
| 1b2fb2ca13694e5cef4973d9d5852b826a86c890 |
|
26-Apr-2014 |
George Mount <mount@google.com> |
Fade Transition sometimes disappeared improperly.
Bug 14320504
Change-Id: I43c2ddd34a5bd3a366027cd3c09d088baa4fb6f4
/frameworks/base/core/java/android/transition/Fade.java
|
| d6107a3170df61d9e776fcd5666acfc9135c6f16 |
|
11-Mar-2014 |
George Mount <mount@google.com> |
Add Transitions useful for Activity transitions.
Slide: transition in and out of the edge of the scene.
Explode: transition to the scene borders
Moved capability from Fade to Visibility.
Change-Id: Ibeb0d8f751c990edc467570d9665fbe251af2703
/frameworks/base/core/java/android/transition/Fade.java
|
| b7a7fc9d233bad507ce893882352618b13647058 |
|
21-Sep-2013 |
Chet Haase <chet@google.com> |
Make fading transitions work better
Previously, a Fade transition would only affect a view if its
parent hierarchy was not also affected between the start/end states.
This caused problems for views which were removed from their parents
between scenes when their parents' visibility also changed between those
scenes. The effect would be that the transition would fade the parent...
but the child would no longer be in that parent, so the user would just see the
child view blink out.
This fix ensure that views are faded appropriately by fading them
regardless the parent hierarchy; if a view is removed from its
parent, fade it out.
Additionally, if that view has not been removed from its parent, but
its parent is no longer parented *and* scene being
transitioned from is based on a layout resource file (and thus
the views are considered temporary after transitioning), then it is
removed from its parent to be faded out in the overlay.
Also, renamed TextChange to ChangeText to be more consistent with
other transition class names.
Change-Id: I4e0e7dfc9e9d95c7a4ca586534b6d204c4f3bae0
/frameworks/base/core/java/android/transition/Fade.java
|
| c46181a963be736186ae29101625a05b5c1f0ba8 |
|
16-Sep-2013 |
Chet Haase <chet@google.com> |
Use transition-only alpha property for fading transitions
The original bug is fixed already, but showed up some problems in
the underlying fade-transition implementation. This fix addresses
those and other issues. The biggest part of the change should help
transition robustness in general, as it removes the dependency on the
public 'alpha' property of views and uses, instead, a new hidden property
on views called 'transitionAlpha'. This is a value which is normally
opaque (1), but which can be used by transitions (only) to animate the
translucency of views without disturbing the actual 'alpha' value which
might be manipulated outside of transitions. This should make transitions
much more robust in general.
In implementing and testing this overall fix, I noticed a couple of things
about transitions that were simply wrong (such as starting fades from the
wrong start value, and incorrectly avoiding transitions on some views
that didn't happen to have ids), and those are fixed in this CL as well.
Issue #10726905 ActionBar weirdness in People app
Issue #10727937 Menu items in gallery appear in faded color after selecting an image/album by long press
Change-Id: If1618446db10c1bfcff4761449241de4f559afc1
/frameworks/base/core/java/android/transition/Fade.java
|
| 23c61f6bc57a611d97d333bce0d8fe00ab81af4c |
|
14-Sep-2013 |
Chet Haase <chet@google.com> |
Ensure that transitions animating alpha end on a reasonable value
The Fade transition sets an initial alpha value of 0 when items are
appearing. This makes items invisible to start with, and then they
eventually fade in as part of the transition when the transition's
animation runs.
But if that animation/transition gets interrupted, or not started, then
the alpha value would not be restored, and the value would stay 0,
making the items invisible indefinitely. This is what was happening in
the action bar of the People app when performing a search.
The fix is to handle Transition and animation events to restore the alpha
to its true value when the transition completes, whether that
transition is canceled or not.
Issue #10726905 ActionBar weirdness in People app
Change-Id: Idb65fd8d471d2ac0a1ddc243fee00ae99f7e72d8
/frameworks/base/core/java/android/transition/Fade.java
|
| d82c8ac4db7091d2e976af4c89a1734465d20cd2 |
|
26-Aug-2013 |
Chet Haase <chet@google.com> |
Transition API changes from API council recommendations
Issue #10460684 KLP API Review: android.view.transition and android.animation
Issue #10570740 Transitions: inflate transition targets from xml
Change-Id: I7a3f6d3aece2fcafc5efd555d033f79e86635c98
/frameworks/base/core/java/android/transition/Fade.java
|