| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
This change also remove trailing whitespace.
Test: code still compiles
Change-Id: I7eff4546320d67d2bae58d31bad0625ea0791b8f
|
| |
|
|
|
|
|
| |
Bug 27367940
Change-Id: I76426def5d4b46c0a0ba534fd952f6c41725c74a
|
| |
|
|
|
|
|
| |
- Move task along a curved path.
Bug: 27607141
Change-Id: I945071de55efed0d327b68045e48fea6989adf63
|
| |
|
|
|
|
|
|
|
| |
Support different interpolators on every keyframe by running
interpolators on proportional duration instead of raw fraction.
Bug: 19928396
Change-Id: Ifb8c3a3b56785582cd6b0121d7bfb44534866300
|
| |
|
|
| |
Change-Id: I031443de83f93eb57a98863001826671b18f3b17
|
| |
|
|
|
|
|
|
| |
For now, only animators use it but we can consider migrating
drawable cache to it as well.
Bug: 17456416
Change-Id: I571b96856805edb171f0fc52e6bff5a365f46b70
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Bug 16984007
Animated Vector Drawables were using the viewport dimensions for
calculating the allowable animation error. Instead of using viewport
dimensions, it is better to use the intrinsic dimensions. Using
the viewport dimensions meant that a small viewport (e.g. 1x1)
would mean that animation paths within would only have an accuracy
of 50% of the dimensions of the drawable.
Change-Id: Id0152eabb4effd1e50c644eea7a371b38baeb7c1
|
| |
|
|
|
|
| |
Bug 17005728
Change-Id: I2e109ed1a3e768e1e0286fc3950516f16509e591
|
| |
|
|
|
| |
Bug: 15710503
Change-Id: Ib39bf0e13199978ffb389111c225beb30312c965
|
| |
|
|
|
|
| |
Issue #8350458 Add exception to Animators when NaN detected
Change-Id: I926c3f35b661b0bb1d9e3c7c0df55e7513734589
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
| |
Change-Id: I316a48273a9cbb428a965e4b849b3e5e9e8202f1
|
| |
|
|
|
|
|
|
|
| |
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
|
| |
|
|
| |
This reverts commit 41f041d9986f8a5d45b6cb0b86e881c81a412168.
|
| |
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
| |
The new animation package's reliance on the old Interpolator interface (in
android.view.animation) was an eyesore. Adding TimeInterpolator, and having the
old Interpolator interface extend it, allows the new Animator classes to break
the tie to the older animation package completely. However, developers can still
use the older Interpolator-based classes, such as AccelerateInterpolator,
because they all implicitly extend the new TimeInterpolator class.
Change-Id: I41132fa56167ba564f4839113289114d0ea31a92
|
| |
|
|
| |
Change-Id: I6a4544875090db485163c8d56de8718f56d267c7
|
| |
|
|
| |
Change-Id: I44c57ee175e8a7bcc4532323ef9b4cfbbf58ae32
|
|
|
Change-Id: I5c8c8037aeeedae1ce7a18200986caf57264772f
|