Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 93001206 authored by Kevin Hufnagle's avatar Kevin Hufnagle Committed by android-build-merger
Browse files

docs: Added note in LayoutTransition class reference that APPEARING and...

docs: Added note in LayoutTransition class reference that APPEARING and DISAPPEARING animation timelines cannot overlap am: 5232329b am: 1456a0a3
am: 4cb05583

Change-Id: I7c28aef0e439a22a74c86cb7cdb4a5c1061bfb50
parents 383483e5 4cb05583
Loading
Loading
Loading
Loading
+5 −1
Original line number Diff line number Diff line
@@ -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