summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
author Kevin Hufnagle <khufnagle@google.com> 2016-09-26 23:13:26 +0000
committer android-build-merger <android-build-merger@google.com> 2016-09-26 23:13:26 +0000
commit1456a0a321b91147941ea3c18e7af087d901d2eb (patch)
tree9dbd022828e8ba223569d562f1d59c0efc6c6493
parentd256aefc3fdfb1dca64e373935c400faf4cca81d (diff)
parent5232329b4e5c00622e3f1d87deec8130aa3b917f (diff)
docs: Added note in LayoutTransition class reference that APPEARING and DISAPPEARING animation timelines cannot overlap
am: 5232329b4e Change-Id: I3e037099a06ca628691c111e065f0c54bc10cb66
-rw-r--r--core/java/android/animation/LayoutTransition.java6
1 files changed, 5 insertions, 1 deletions
diff --git a/core/java/android/animation/LayoutTransition.java b/core/java/android/animation/LayoutTransition.java
index cdd72be76805..5a23fddf1d51 100644
--- a/core/java/android/animation/LayoutTransition.java
+++ b/core/java/android/animation/LayoutTransition.java
@@ -62,7 +62,11 @@ import java.util.Map;
* layout will run (closing the gap created in the layout when the item was removed). If this
* default choreography behavior is not desired, the {@link #setDuration(int, long)} and
* {@link #setStartDelay(int, long)} of any or all of the animations can be changed as
- * appropriate.</p>
+ * appropriate. Keep in mind, however, that if you start an APPEARING animation before a
+ * DISAPPEARING animation is completed, the DISAPPEARING animation stops, and any effects from
+ * the DISAPPEARING animation are reverted. If you instead start a DISAPPEARING animation
+ * before an APPEARING animation is completed, a similar set of effects occurs for the
+ * APPEARING animation.</p>
*
* <p>The animations specified for the transition, both the defaults and any custom animations
* set on the transition object, are templates only. That is, these animations exist to hold the