Android/frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: Added note in LayoutTransition class reference that APPEARING

Browse Source 
and DISAPPEARING animation timelines cannot overlap

Bug: 16808571
Change-Id: I8cbac11da4f866f2d3bcde45996b039e9bdfb801
This commit is contained in:
Kevin Hufnagle
2016-09-19 12:02:33 -07:00
parent f032cbfafc
commit 5232329b4e
1 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
core/java/android/animation/LayoutTransition.java
View File

@@ -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 * 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 * 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 * {@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 * <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 * set on the transition object, are templates only. That is, these animations exist to hold the