History log of /frameworks/base/core/java/android/animation/ObjectAnimator.java
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
3c8598399638c90da69e14fde824385fdb582e1d 28-May-2016 Doris Liu <tianliu@google.com> Add more doc for Object animators defined with a single value

Bug: 28104516
Change-Id: I181b2817ceda5dfaf87e12c81b21e7d0d2f002fc
/frameworks/base/core/java/android/animation/ObjectAnimator.java
fa21bdfd5a8a5da3ec0530f7cc884994f92dc597 22-Apr-2016 Chet Haase <chet@google.com> Document behavior of object references in Animator classes

Animators that are created with Object values may have undefined
behavior when those objects are changed outside of the animator itself.
For example, an animator created with a start Rect and end Rect
will animate the bounds between those two objects. But if the caller
changes either the start or end rect before or during the animation,
that will affect the values used on every frame of the animation.

Issue #28304520 Strange interpolation of property values holder values

Change-Id: Id6ac19c8369ae34450e6b53d68f5e492b27c577e
/frameworks/base/core/java/android/animation/ObjectAnimator.java
e60a693d847a160b7a0d70046eb1d0e6d2cb4f10 17-Mar-2016 Chet Haase <chet@google.com> Clarify docs around weak references to animator targets

Issue #26069047 Weak reference to the target in animators
can cause interrupted animations

Change-Id: I719f619006e93a94af907c4de7840c691a5aed37
/frameworks/base/core/java/android/animation/ObjectAnimator.java
d98f4ba86c02714d94ec3b6f35345cb0b04f7778 14-Mar-2016 George Mount <mount@google.com> Add @SafeVarargs for methods using typevar varargs.

Bug 27142336
Using a type variable in a varargs leads to a javac warning
because type variables are treated as Object after compilation.
Because these uses do not require a specific typed array, we
can use @SafeVarargs to suppress the warning.

Change-Id: I860bcc79667a9c85c381c7994fd1d798209d7c66
/frameworks/base/core/java/android/animation/ObjectAnimator.java
f2aeca34ba55d56de0c0db7c126f98a8f623f002 16-Oct-2015 George Mount <mount@google.com> Change wrong doc about using linear interpolator.

Bug 24986885

Change-Id: I79f2cd0c6439749bf1fc412d28471e865501aa5a
/frameworks/base/core/java/android/animation/ObjectAnimator.java
3618d30f8ab6018025b11869676b309c3b4961cf 14-Aug-2015 Doris Liu <tianliu@google.com> Internal cleanup for Animator framework

This CL includes the following changes:
1) Remove redundant field mPlayingState in ValueAnimator.
2) Refactor AnimationHandler so that all of its interaction with Choreographer
is through an interface. A custom provider that implements this interface can
be plugged in and provide timing pulse that are independent of Choreographer.
3) Better encapsulate AnimationHandler and ValueAnimator. Interaction between
the two is done through register/unregister frame callbacks as well as
AnimationFrameCallback interface.
4) Change how animation delay is handled.

Change-Id: Icd49f727321c362dab49b5b33815333c9ea559e0
/frameworks/base/core/java/android/animation/ObjectAnimator.java
6aac06ab940566020d050fdaa0d5e8d2e6c128ae 01-Apr-2015 Doris Liu <tianliu@google.com> Add per-interval interpolation support for keyframe in xml resources

Bug: 19913234
Change-Id: Ie46af02b2db3dad6ace667480aa556e0f645d278
/frameworks/base/core/java/android/animation/ObjectAnimator.java
c615c6fc9caca76cd96998f86e1f1e6393aeadbb 02-Mar-2015 Tor Norbye <tnorbye@google.com> Annotate methods to be called from overrides with @CallSuper

Change-Id: Ibc587c2aaee9f3e7f448079f72a75459fe4e15e7
/frameworks/base/core/java/android/animation/ObjectAnimator.java
08c7116ab9cd04ad6dd3c04aa1017237e7f409ac 28-Feb-2015 John Spurlock <jspurlock@google.com> Remove unused imports in frameworks/base.

Change-Id: I031443de83f93eb57a98863001826671b18f3b17
/frameworks/base/core/java/android/animation/ObjectAnimator.java
d430753cba09acb07af8b313286f247c78a41a32 01-Dec-2014 Chet Haase <chet@google.com> Add resource attributes for Keyframes and PropertyValuesHolders

Issue #17939329 Expose multi-property and multi-keyframe capabilities in animation resources

Change-Id: I14822ced47665fa6cde4996f74d3078da2ada38a
/frameworks/base/core/java/android/animation/ObjectAnimator.java
e48ef2a3efedebdcc351b60d2f3c35c987811938 31-Oct-2014 George Mount <mount@google.com> Cancel animation when target changes.

Bug 18201083

Change-Id: I2ea15063b18881c4b31ae6cdc287649dbc4a61f7
/frameworks/base/core/java/android/animation/ObjectAnimator.java
984011f6850fd4b6ad4db6d6022bd475d7a2c712 21-Aug-2014 George Mount <mount@google.com> Use optimized Keyframes for Path animations.

Bug 17005728

Change-Id: I2e109ed1a3e768e1e0286fc3950516f16509e591
/frameworks/base/core/java/android/animation/ObjectAnimator.java
8619f48fb353740f7fd3f6eaa86fe493377e6cad 16-Jul-2014 Yigit Boyar <yboyar@google.com> Change Animators to reset values when restarted if their target changes

Bug: 15710503
Change-Id: Ib39bf0e13199978ffb389111c225beb30312c965
/frameworks/base/core/java/android/animation/ObjectAnimator.java
f505b1f08d606688881d56591d018c0d9162d739 23-Jun-2014 George Mount <mount@google.com> Use Property for ofFloat with Path.

Bug 15827972

Change-Id: I8917f7ab0df9709c11ae38e89af6b603ec76d430
/frameworks/base/core/java/android/animation/ObjectAnimator.java
87ac5f60e20fba335497aa9dc03b7c29c4b966a2 05-Jun-2014 Alan Viverette <alanv@google.com> Use a weak reference to the ObjectAnimator target

Also adds Nullable and NonNull annotations where it was obvious.

Change-Id: I4be7a94b0510e87b260f902cc1efd3c5e4bdc228
/frameworks/base/core/java/android/animation/ObjectAnimator.java
42516d19db936b10874c27e16eeacda041af01f9 20-May-2014 George Mount <mount@google.com> API Review: split out BidirectionalTypeConverter.

Bug 14997858

Change-Id: I1f2ccf7c4e60320c8df759702a8f2fa24fd3acd2
/frameworks/base/core/java/android/animation/ObjectAnimator.java
c96c7b2e54965e30c8fb82295f1ca9f891ebd5e7 23-Aug-2013 George Mount <mount@google.com> Add animations along a Path.

Change-Id: If03bd10a3961ff874e33489e1253146b8dadca33
/frameworks/base/core/java/android/animation/ObjectAnimator.java
1ffb280a7d2c70cc16d709c685f5d31fdb86b5e4 10-Oct-2013 George Mount <mount@google.com> Add ofArgb to ObjectAnimator and ValueAnimator.

Bug 10396985

Change-Id: Ib1fcea04b5a915800fc415b3d548a8853b05389c
/frameworks/base/core/java/android/animation/ObjectAnimator.java
4eed52944c0fcb3afa7369aba60fb5c655580286 30-Aug-2013 George Mount <mount@google.com> Support for multiple value animations.

Bug 2805977
Support for multi-value setters in ObjectAnimator.

Change-Id: I7854dfcb82372afc6d9afb4c50a289ff9d41574e
/frameworks/base/core/java/android/animation/ObjectAnimator.java
16d2c9cc6bd67131d9921fbc14a69d88f48f48ca 17-Sep-2013 George Mount <mount@google.com> Setter values can now have different type than animated values.

Add TypeConverter to convert animated values type to target
setter type.

Change-Id: I7f0581b18a5321b4aafd7e47f147a81573c45061
/frameworks/base/core/java/android/animation/ObjectAnimator.java
fdd3ad7018ebb054c0288b8cd92739703a973181 25-Apr-2013 Chet Haase <chet@google.com> Give animators more useful names in systrace

Also, fix ObjectAnimator.getPropertyName() to return useful info
for ObjectAnimators not created with string-based property names.

Change-Id: If7ab6dbcc3be13f5978840b02f4a91ef7eee1c50
/frameworks/base/core/java/android/animation/ObjectAnimator.java
be19e030a14c8e398e8af97fa898ea80187704df 16-Mar-2013 Chet Haase <chet@google.com> Add auto-cancel ability to ObjectAnimator

Add a method that enables a new auto-cancel option to
ObjectAnimator. When set, any ObjectAnimator (when started) will
cause any running ObjectAnimator instance (with that flag set)
that has the same target and properties to cancel() itself prior
to starting the new one.

Issue #7426129 Add auto-cancel to animators

Change-Id: I586659c365289cdb9afb6c416bdbaf5630477149
/frameworks/base/core/java/android/animation/ObjectAnimator.java
3aef8e1d1b2f0b87d470bcccf37ba4ebb6560c45 20-Dec-2011 Joe Fernandez <joefernandez@google.com> docs: Add developer guide cross-references, Project ACRE, round 4

Change-Id: I1b43414aaec8ea217b39a0d780c80a25409d0991
/frameworks/base/core/java/android/animation/ObjectAnimator.java
3c4ce72c4d66d9ee041924259f20381b658c1529 03-Sep-2011 Chet Haase <chet@google.com> Fix artifact with LayoutTransitions on disappearing window.

Logic in performTraversals() starts a transition running at the
proper time. But when a view's parent window goes away, this transition
may not start at that time because drawing gets canceled. But the
transition still hung off of the ViewRoot, waiting until some later
drawing operation to kick it off. This resulted in some weird animations
like the Recents panel appearing and having a single item animate off of it.

The fix is to delete pending transitions when drawing is skipped.

Change-Id: I3ab7702c16e069644a163424f977350743e2cecc
/frameworks/base/core/java/android/animation/ObjectAnimator.java
b39f051631250c49936a475d0e64584afb7f1b93 24-May-2011 Chet Haase <chet@google.com> Add 'Property' object

This change adds a generic Property facility to the SDK, which allows an
easy way to reference fields (private or otherwise) in a general way.
For example, animations can use this facility to animate 'properties'
on target objects in a way that is more code- and compiler-friendly than
the existing String-based approach (for objects which have implemented
Properties, of course). The animator classes have been updated to use
this new approach (in addition to Strings, which are still more generally
useful for objects which have get/set functions but not Property objects).

The change also includes new Property objects on View (which can now be
used in creating animations on Views).

There is an unrelated change on GLES20RecordingCanvas to change the way we
cache bitmaps, which avoids spurious garbage by using an ArrayList instead of
a HashSet.

Change-Id: I167b43a3fca20e7695b1a23ca81274367539acda
/frameworks/base/core/java/android/animation/ObjectAnimator.java
e9140a72b1059574046a624b471b2c3a35806496 17-Feb-2011 Chet Haase <chet@google.com> Fix invalidation bug with View bounds properties

When setLeft/Right/Top/Bottom() functions were called on View,
invalidation was only happening at the parent level. When an
app is hardware accelerated, this means that the view's display
list is not being recreated. So views that were changing size due
to these calls were not getting redrawn properly, causing some
artifacts in animations (especially LayoutTransition, which
calls these setters).

Fix is to invalidate the child instead of just the child's bounds
in the parent.

Change-Id: Ic8b2a5db519345dce617f914c2214738f22031b2
/frameworks/base/core/java/android/animation/ObjectAnimator.java
7beecfaf3b65a1552a7a7cc78ca00bb04133b507 16-Jan-2011 Patrick Dubroy <dubroy@google.com> Fix latent bug with reinitializing an ObjectAnimator.
/frameworks/base/core/java/android/animation/ObjectAnimator.java
51ae5fc2d22a7bb616f432d7bac66bbbf8a1927f 16-Jan-2011 Patrick Dubroy <dubroy@google.com> Fix animation bugs caused by weak reference

Change-Id: I4c7bd9d4843c355efd9c89059462f19600c3be45
/frameworks/base/core/java/android/animation/ObjectAnimator.java
2b90a9a7144f1bb91f72da025ce444038f12c6aa 15-Jan-2011 Scott Main <smain@google.com> fix sdk build breakage; remove invalid @note tag

Change-Id: Iaaf5a38388ceccdd0d1f3766523788f54f1dc8d2
/frameworks/base/core/java/android/animation/ObjectAnimator.java
ec84c3a189e4aa70aa6ea8ba712e5a4f260a153b 14-Jan-2011 Patrick Dubroy <dubroy@google.com> Allow old view hierarchy to be GC'ed more quickly during rotation.
/frameworks/base/core/java/android/animation/ObjectAnimator.java
e2ab7ccd385cdb6517955c719e1d2b49771bedb6 07-Dec-2010 Chet Haase <chet@google.com> Change cancel/end behavior of animations to be synchronous

Previously, cancel() and end() calls would simply log a message to
be handled later by the animation handler. This caused problems with
coordinating complex animations, where some start() events for
future animations would occur before end() events for animations already
completed.
The change is to make these events synchronous (and require them to be
called from the appropriate thread), simplifying the code and the usage.

Also, fixed various timing and event bugs in AnimatorSet, and removed
the getter/setter properties from ObjectAnimator, since an earlier change
makes these properties undesirable (because the code will use a faster
JNI approach instead of reflection when it can).

Change-Id: I05c16645c2a31a92048a6031ddb126eb4312a946
/frameworks/base/core/java/android/animation/ObjectAnimator.java
6e0ecb4eed5cd2e1f15766d7028467129974a12d 04-Nov-2010 Chet Haase <chet@google.com> Adding JNI methods as a faster reflection mechanism

This approach is only for the common cases of void-return,
single-argument float/int methods.

Change-Id: Ifb31535a6f717b85417eced93c579be6e461e039
/frameworks/base/core/java/android/animation/ObjectAnimator.java
7c608f25d494c8a0a671e7373efbb47ca635367e 23-Oct-2010 Chet Haase <chet@google.com> optimizing for primitive types in animations

The animator classes caused autoboxing by converting primitive types (by far
the most typical types used in animations) to be converted to their
Object equivalents because of various APIs that required Object
(like getValue() to get the animated value). This change creates
factory methods on some classes instead of the former constructors
so that we can create and return private type-specific subclasses
which operate directly on the primitive types instead.

In particular, float and int are natively supported by the animators
now. Support in the APIs for double and long was removed because it
seemed like these less common types did not justify the extra
baggage of the added API and code.

Change-Id: I6008a3883e3d6dd5225005f45f112af148e5a4ea
/frameworks/base/core/java/android/animation/ObjectAnimator.java
70d4ba15b1f0c1133c5aabc86de828b41e482fff 06-Oct-2010 Chet Haase <chet@google.com> Performance optimizations for animations and toolkit

Change-Id: I316a48273a9cbb428a965e4b849b3e5e9e8202f1
/frameworks/base/core/java/android/animation/ObjectAnimator.java
2794eb3b02e2404d453d3ad22a8a85a138130a07 13-Oct-2010 Chet Haase <chet@google.com> Remove generics from Animator APIs

Change the manner of constructing Animator-related objects from constructors
via generics to factory methods with type-specific method names. Should
improve the proliferation of warnings due to generics issues and make the
code more readable (less irrelevant angle brackets Floating around).

Change-Id: Ib59a7dd72a95d438022e409ddeac48853082b943
/frameworks/base/core/java/android/animation/ObjectAnimator.java
83d6e8213230fb0805aa019d266842253baeb114 14-Oct-2010 Romain Guy <romainguy@google.com> Revert "Remove generics from Animator APIs"

This reverts commit 41f041d9986f8a5d45b6cb0b86e881c81a412168.
/frameworks/base/core/java/android/animation/ObjectAnimator.java
41f041d9986f8a5d45b6cb0b86e881c81a412168 13-Oct-2010 Chet Haase <chet@google.com> Remove generics from Animator APIs

Change the manner of constructing Animator-related objects from constructors
via generics to factory methods with type-specific method names. Should
improve the proliferation of warnings due to generics issues and make the
code more readable (less irrelevant angle brackets Floating around).

Change-Id: I7c1776b15f3c9f245c09fb7de6dc005fdba58fe2
/frameworks/base/core/java/android/animation/ObjectAnimator.java
0e0590bf3cb32e73f423c0fe39a180d4b3c4343d 26-Sep-2010 Chet Haase <chet@google.com> bug fixes in animation classes

Change-Id: I5465bc95032c94851b8cf4e4db3477f546e8b0d1
/frameworks/base/core/java/android/animation/ObjectAnimator.java
a18a86b43e40e3c15dcca0ae0148d641be9b25fe 07-Sep-2010 Chet Haase <chet@google.com> Rename several animation classes

Change-Id: I6a4544875090db485163c8d56de8718f56d267c7
/frameworks/base/core/java/android/animation/ObjectAnimator.java