frameworks_base.git - frameworks

	Commit message (Collapse)	Author	Age	Files	Lines
*	Simplify KeyframeSet to avoid caching.	George Mount	2016-06-08	1	-26/+0
\| \| \| \| \| \| \|	Bug 27367940 Change-Id: I76426def5d4b46c0a0ba534fd952f6c41725c74a
*	Fix per-keyframe interpolators	Doris Liu	2015-03-30	1	-3/+4
\| \| \| \| \| \| \| \| \|	Support different interpolators on every keyframe by running interpolators on proportional duration instead of raw fraction. Bug: 19928396 Change-Id: Ifb8c3a3b56785582cd6b0121d7bfb44534866300
*	Remove unused imports in frameworks/base.	John Spurlock	2015-02-28	1	-1/+0
\| \| \| \|	Change-Id: I031443de83f93eb57a98863001826671b18f3b17
*	Added a generic configuration and theme based cache	Yigit Boyar	2014-10-23	1	-1/+2
\| \| \| \| \| \| \| \|	For now, only animators use it but we can consider migrating drawable cache to it as well. Bug: 17456416 Change-Id: I571b96856805edb171f0fc52e6bff5a365f46b70
*	Use optimized Keyframes for Path animations.	George Mount	2014-08-29	1	-2/+7
\| \| \| \| \| \|	Bug 17005728 Change-Id: I2e109ed1a3e768e1e0286fc3950516f16509e591
*	Change Animators to reset values when restarted if their target changes	Yigit Boyar	2014-07-16	1	-0/+5
\| \| \| \| \|	Bug: 15710503 Change-Id: Ib39bf0e13199978ffb389111c225beb30312c965
*	Fix when >2 keyframes supplied	Chet Haase	2011-02-11	1	-3/+3
\| \| \| \| \| \| \| \| \| \| \| \| \| \|	When there are more than two keyframes, we treat each keyframe interval as its own separate period during which to calculate animated values. To do this, we calculate an intervaleFraction from the overall elapsed fraction of the entire animation. This intervalFraction is then used to calculate the animated values in that interval. However, we failed to actually use the intervalFraction in some code paths, using the overall fraction instead. This caused a jumping behavior because we were incorrectly calculating the values during the intervals. Change-Id: Ia052e1e8b5130ff450ee20c0a3581e3de42399e1
*	Remove obsolete DoubleEvaluator	Chet Haase	2011-01-16	1	-2/+2
\| \| \| \|	Change-Id: I4407468599061ff35c68589988fb1e897de28c69
*	optimizing for primitive types in animations	Chet Haase	2010-11-03	1	-0/+133
	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