From 5232329b4e5c00622e3f1d87deec8130aa3b917f Mon Sep 17 00:00:00 2001 From: Kevin Hufnagle Date: Mon, 19 Sep 2016 12:02:33 -0700 Subject: docs: Added note in LayoutTransition class reference that APPEARING and DISAPPEARING animation timelines cannot overlap Bug: 16808571 Change-Id: I8cbac11da4f866f2d3bcde45996b039e9bdfb801 --- core/java/android/animation/LayoutTransition.java | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) 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.

+ * 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.

* *

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 -- cgit v1.2.3-59-g8ed1b