最近又用到了动画，决定把几次项目里用到的动画走过的弯路总结一下，顺便梳理下Android的动画体系。众所周知，android动画分三类：一是View 动画，又叫Tween动画，二是frame 动画(帧动画)，又叫drawable 动画，三是属性动画，即property animation.
View动画，根据作用又分为缩放动画ScaleAnimation／移位动画TranslateAnimation ／ 透明度动画AlphaAnimation ／ 旋转动画RotateAnimation，这四个动画都继承android.view.animation下的Animation类。继承Animation的除了这四个类外，还有AnimationSet，关系图如下所示：
帧动画 对应AnimationDrawable类，继承自DrawableContainer，通过加载多个Drawable来一帧一帧播放达到动画效果。尽管很多人觉得这个不值一提，但是某些动画效果，如显示个小羊吃草还必须得用这个动画。
接下来进入正题谈属性动画，该动画从android3.0引入，API11引入，是为了弥补view动画的不足。正式项目里用的话为了兼容android2.3可以用NineOldAndroids，直接将生成的jar包放进去就ok了。
属性动画都在android.animation包下，基类是Animator类，子类为ValueAnimator和AnimatorSet（作用同view动画的AnimationSet相同），ValueAnimator的子类有ObjectAnimator和TimeAnimator，一般我们用属性动画ObjectAnimator就ok了。不妨简单对比下和view动画架构上的异同：
View动画，包名android.view.animation,基类为Animation，核心子类为TranslateAnimation，ScaleAnimation，AlphaAnimation，RotateAnimation及AnimationSet。
Property动画，包名android.animation，基类为Animator，核心子类为AnimatorSet，ValueAnimator，ObjectAnimator，TimeAnimator。
在详细对比属性动画和view动画前，先介绍个函数setTranslationX和setTranslationY，api版本为11，是设置view相对原始位置的偏移量，正式项目用的话考虑到兼容api11之前的用nineoldandroids里的ViewHelper即可。
public void setTranslationX (float translationX)
Added in API level 11
Sets the horizontal location of this view relative to its left position. This effectively positions the object post-layout, in addition to wherever the object's layout placed it.
Related XML Attributes
android:translationX
Parameters
translationX The horizontal position of this view relative to its left position, in pixels.
上面是api介绍，即相对left position的偏移，所谓left position也即getLeft()，同时可以在xml里直接用android:translationX进行设置。关于view的位置，我们最常用的莫过于android:layoutMargin这一套，用来设置相对父布局的偏移，在Java代码里可以通过新建或更新view的LayoutParams进行修改,如下所示：
LinearLayout.LayoutParams params = (LinearLayout.LayoutParams)text.getLayoutParams()
params.leftMargin = 0
params.rightMargin = 0
params.setMargins(0, 0, 0, 0)
text.setLayoutParams(params)
之所以说有时需要新建Params而有时候需要更新，是因为有时候从view取来的params是空的，这个日后开篇文章专门谈这个问题。总之，通过view的LayoutParams设置margin最终影响了view的位置，这个同时会改变view的getLeft／getRight等变量。但通过setTranslationX改变view的位置，是不改变view的LayoutParams的，也即不改变getLeft等view的信息。 但他确实改变了view的位置，这一点可以通过获取其在window或screen的坐标，或通过getLocationInWindow及如下所示的api等到view的精确位置：
text.getLocationInWindow(pos);
text.getLocationOnScreen(pos);
text.getLocalVisibleRect()
text.getGlobalVisibleRect()
总结：
1，setTranslationX改变了view的位置，但没有改变view的LayoutParams里的margin属性；
2，它改变的是android:translationX 属性，也即这个参数级别是和margin平行的。
下面来看这个例子，通过点击按键让一个view从最左边移动到屏幕的最右边，分别用view的TranslateAnimation和属性动画来实现。
布局代码：
<RelativeLayout xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:tools="http://schemas.android.com/tools"
android:layout_width="match_parent"
android:layout_height="match_parent"
tools:context=".MainActivity">
<LinearLayout
android:layout_width="match_parent"
android:layout_height="50dp"
android:background="@android:color/holo_green_light"
android:orientation="vertical">
<TextView
android:id="@+id/text"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:text="@string/hello_world" />
</LinearLayout>
<Button
android:id="@+id/btn_start_anim"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_centerInParent="true"
android:text="属性动画" />
<Button
android:id="@+id/btn_start_anim2"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_toLeftOf="@id/btn_start_anim"
android:layout_centerVertical="true"
android:layout_marginRight="40dp"
android:text="复位" />
<Button
android:id="@+id/btn_reset_pos"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_toRightOf="@id/btn_start_anim"
android:layout_centerVertical="true"
android:layout_marginLeft="40dp"
android:text="复位" />
</RelativeLayout>
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18
- 19
- 20
- 21
- 22
- 23
- 24
- 25
- 26
- 27
- 28
- 29
- 30
- 31
- 32
- 33
- 34
- 35
- 36
- 37
- 38
- 39
- 40
- 41
- 42
- 43
- 44
- 45
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18
- 19
- 20
- 21
- 22
- 23
- 24
- 25
- 26
- 27
- 28
- 29
- 30
- 31
- 32
- 33
- 34
- 35
- 36
- 37
- 38
- 39
- 40
- 41
- 42
- 43
- 44
- 45
Java代码：
MainActivity.java
package com.example.yanzi.myapplication;
import android.os.Bundle;
import android.support.v7.app.ActionBarActivity;
import android.util.Log;
import android.view.View;
import android.view.animation.TranslateAnimation;
import android.widget.Button;
import android.widget.LinearLayout;
import android.widget.TextView;
import android.widget.Toast;
import com.nineoldandroids.animation.Animator;
import com.nineoldandroids.animation.ObjectAnimator;
import com.nineoldandroids.view.ViewHelper;
import com.yanzi.util.UiUtil;
public class MainActivity extends ActionBarActivity implements View.OnClickListener{
private static final String TAG = "YanZi";
Button btn_start_anim;
Button btn_reset_pos;
Button btn_start_anim2;
TextView text;
@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_main);
initData();
initUI();
}
private void initData(){
UiUtil.initialize(getApplicationContext());
}
private void initUI(){
btn_start_anim = (Button)findViewById(R.id.btn_start_anim);
btn_start_anim.setOnClickListener(this);
btn_start_anim2 = (Button)findViewById(R.id.btn_start_anim2);
btn_start_anim2.setOnClickListener(this);
btn_reset_pos = (Button)findViewById(R.id.btn_reset_pos);
btn_reset_pos.setOnClickListener(this);
text = (TextView)findViewById(R.id.text);
text.setOnClickListener(this);
LinearLayout.LayoutParams params = (LinearLayout.LayoutParams)text.getLayoutParams();
params.leftMargin = 0;
params.rightMargin = 0;
params.setMargins(0, 0, 0, 0);
text.setLayoutParams(params);
}
@Override
public void onClick(View v) {
switch (v.getId()){
case R.id.btn_start_anim:
playAnim1();
break;
case R.id.btn_start_anim2:
playAnim2();
break;
case R.id.btn_reset_pos:
resetPos();
break;
case R.id.text:
printParams();
break;
default:break;
}
}
public void printParams(){
LinearLayout.LayoutParams params = (LinearLayout.LayoutParams)text.getLayoutParams();
if(params != null){
String s = "leftMargin = " + params.leftMargin + " rightMargin = " + params.rightMargin
+ " getLeft = " + text.getLeft() + " getRight = " + text.getRight() + " getWidth = " + text.getWidth();
Log.i(TAG, s);
int[] pos = new int[2];
text.getLocationInWindow(pos);
Log.i(TAG, "location, x = " + pos[0] + " y = " + pos[1]);
Toast.makeText(getApplicationContext(), s, Toast.LENGTH_LONG).show();
}
}
private void playAnim1(){
int w = text.getWidth();
int screenW = UiUtil.getScreenWidth();
int transX = screenW - w;
ObjectAnimator transAnim = ObjectAnimator.ofFloat(text, "translationX", 0, transX);
transAnim.addListener(new Animator.AnimatorListener() {
@Override
public void onAnimationStart(Animator animator) {
}
@Override
public void onAnimationEnd(Animator animator) {
}
@Override
public void onAnimationCancel(Animator animator) {
}
@Override
public void onAnimationRepeat(Animator animator) {
}
});
transAnim.setDuration(300);
transAnim.start();;
}
private void playAnim2(){
int w = text.getWidth();
int screenW = UiUtil.getScreenWidth();
int transX = screenW - w;
TranslateAnimation transAnim = new TranslateAnimation(0, transX, 0, 0);
transAnim.setDuration(300);
text.setAnimation(transAnim);
transAnim.start();
}
private void resetPos(){
ViewHelper.setTranslationX(text, 0);
}
}
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18
- 19
- 20
- 21
- 22
- 23
- 24
- 25
- 26
- 27
- 28
- 29
- 30
- 31
- 32
- 33
- 34
- 35
- 36
- 37
- 38
- 39
- 40
- 41
- 42
- 43
- 44
- 45
- 46
- 47
- 48
- 49
- 50
- 51
- 52
- 53
- 54
- 55
- 56
- 57
- 58
- 59
- 60
- 61
- 62
- 63
- 64
- 65
- 66
- 67
- 68
- 69
- 70
- 71
- 72
- 73
- 74
- 75
- 76
- 77
- 78
- 79
- 80
- 81
- 82
- 83
- 84
- 85
- 86
- 87
- 88
- 89
- 90
- 91
- 92
- 93
- 94
- 95
- 96
- 97
- 98
- 99
- 100
- 101
- 102
- 103
- 104
- 105
- 106
- 107
- 108
- 109
- 110
- 111
- 112
- 113
- 114
- 115
- 116
- 117
- 118
- 119
- 120
- 121
- 122
- 123
- 124
- 125
- 126
- 127
- 128
- 129
- 130
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18
- 19
- 20
- 21
- 22
- 23
- 24
- 25
- 26
- 27
- 28
- 29
- 30
- 31
- 32
- 33
- 34
- 35
- 36
- 37
- 38
- 39
- 40
- 41
- 42
- 43
- 44
- 45
- 46
- 47
- 48
- 49
- 50
- 51
- 52
- 53
- 54
- 55
- 56
- 57
- 58
- 59
- 60
- 61
- 62
- 63
- 64
- 65
- 66
- 67
- 68
- 69
- 70
- 71
- 72
- 73
- 74
- 75
- 76
- 77
- 78
- 79
- 80
- 81
- 82
- 83
- 84
- 85
- 86
- 87
- 88
- 89
- 90
- 91
- 92
- 93
- 94
- 95
- 96
- 97
- 98
- 99
- 100
- 101
- 102
- 103
- 104
- 105
- 106
- 107
- 108
- 109
- 110
- 111
- 112
- 113
- 114
- 115
- 116
- 117
- 118
- 119
- 120
- 121
- 122
- 123
- 124
- 125
- 126
- 127
- 128
- 129
- 130
用到了一个辅助类获得屏幕的宽高和dip转px：
package com.yanzi.util;
import android.content.Context;
import android.util.DisplayMetrics;
import android.util.Log;
import android.view.View;
import android.view.ViewGroup;
import android.view.WindowManager;
import android.widget.ListAdapter;
import android.widget.ListView;
public class UiUtil {
private static final String TAG = "YanZi_UiUtil";
private static int screenWidth = 0;
private static int screenHeight = 0;
private static float screenDensity = 0;
private static int densityDpi = 0;
private static int statusBarHeight = 0;
public static void initialize(Context context){
if (context == null)
return;
DisplayMetrics metrics = new DisplayMetrics();
WindowManager wm = (WindowManager)context.getSystemService(Context.WINDOW_SERVICE);
wm.getDefaultDisplay().getMetrics(metrics);
screenWidth = metrics.widthPixels;
screenHeight = metrics.heightPixels;
screenDensity = metrics.density;
densityDpi = metrics.densityDpi;
Log.i(TAG, "screenDensity = " + screenDensity + " densityDpi = " + densityDpi);
}
public static int dip2px(float dipValue){
return (int)(dipValue * screenDensity + 0.5f);
}
public static int px2dip(float pxValue){
return (int)(pxValue / screenDensity + 0.5f);
}
public static int getScreenWidth() {
return screenWidth;
}
public static int getScreenHeight() {
return screenHeight;
}
}
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18
- 19
- 20
- 21
- 22
- 23
- 24
- 25
- 26
- 27
- 28
- 29
- 30
- 31
- 32
- 33
- 34
- 35
- 36
- 37
- 38
- 39
- 40
- 41
- 42
- 43
- 44
- 45
- 46
- 47
- 48
- 49
- 50
- 51
- 52
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18
- 19
- 20
- 21
- 22
- 23
- 24
- 25
- 26
- 27
- 28
- 29
- 30
- 31
- 32
- 33
- 34
- 35
- 36
- 37
- 38
- 39
- 40
- 41
- 42
- 43
- 44
- 45
- 46
- 47
- 48
- 49
- 50
- 51
- 52
运行界面：
大概说下里面核心的几个函数：
1，使用view动画TranslateAnimation：
private void playAnim2(){
int w = text.getWidth();
int screenW = UiUtil.getScreenWidth();
int transX = screenW - w;
TranslateAnimation transAnim = new TranslateAnimation(0, transX, 0, 0);
transAnim.setDuration(300);
text.startAnimation(transAnim);
}
2,使用属性动画移位：
private void playAnim1(){
int w = text.getWidth();
int screenW = UiUtil.getScreenWidth();
int transX = screenW - w;
ObjectAnimator transAnim = ObjectAnimator.ofFloat(text, "translationX", 0, transX);
transAnim.addListener(new Animator.AnimatorListener() {
@Override
public void onAnimationStart(Animator animator) {
}
@Override
public void onAnimationEnd(Animator animator) {
}
@Override
public void onAnimationCancel(Animator animator) {
}
@Override
public void onAnimationRepeat(Animator animator) {
}
});
transAnim.setDuration(300);
transAnim.start();;
}
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18
- 19
- 20
- 21
- 22
- 23
- 24
- 25
- 26
- 27
- 28
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18
- 19
- 20
- 21
- 22
- 23
- 24
- 25
- 26
- 27
- 28
3,点击text打印它的坐标：
public void printParams(){
LinearLayout.LayoutParams params = (LinearLayout.LayoutParams)text.getLayoutParams()
if(params != null){
String s = "leftMargin = " + params.leftMargin + " rightMargin = " + params.rightMargin
+ " getLeft = " + text.getLeft() + " getRight = " + text.getRight() + " getWidth = " + text.getWidth()
Log.i(TAG, s)
int[] pos = new int[2]
text.getLocationInWindow(pos)
Log.i(TAG, "location, x = " + pos[0] + " y = " + pos[1])
Toast.makeText(getApplicationContext(), s, Toast.LENGTH_LONG).show()
}
}
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
4,使用属性动画后如果想复位：
private void resetPos(){
ViewHelper.setTranslationX(text, 0);
}
直接将translationX设为0即可，而不是上次偏移量的相反数。正因为如此，重复点击属性动画，看到view每次都从最左边到最右边，并最终停在最右边。因为属性动画的执行过程就是setTranslationX(0), 1, 2, 3, 4,……..N的过程，所以才会有看到的效果。
另外，可以看到使用view的TranslateAnimation动画播放完毕后，view瞬间又回到了原点；而使用属性动画移位后view位置确实发生了改变。但LayoutParams里的margin和getLeft信息并未改变。有没有办法让view的TranslateAnimation播放完毕后，停在那个地方呢？
肯定是有，加上这句话：transAnim.setFillAfter(true);之后运行发现view确实停在了屏幕的右侧，但是点击右侧的textview并没有触发打印参数的函数，而点击textview的初始位置才触发。所以它并没有改变view的位置，仅仅是绘制在了屏幕的右侧。因此，如果使用view动画但又想真正改变view位置需要如下代码：
private void playAnim2(){
int w = text.getWidth();
int screenW = UiUtil.getScreenWidth();
int transX = screenW - w;
TranslateAnimation transAnim = new TranslateAnimation(0, transX, 0, 0);
transAnim.setDuration(300);
transAnim.setAnimationListener(new Animation.AnimationListener() {
@Override
public void onAnimationStart(Animation animation) {
}
@Override
public void onAnimationEnd(Animation animation) {
updateParams();
}
@Override
public void onAnimationRepeat(Animation animation) {
}
});
text.startAnimation(transAnim);
}
private void updateParams(){
int w = text.getWidth();
int screenW = UiUtil.getScreenWidth();
LinearLayout.LayoutParams params = (LinearLayout.LayoutParams) text.getLayoutParams();
params.leftMargin = screenW - w;
text.setLayoutParams(params);
}
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18
- 19
- 20
- 21
- 22
- 23
- 24
- 25
- 26
- 27
- 28
- 29
- 30
- 31
- 32
- 33
- 34
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18
- 19
- 20
- 21
- 22
- 23
- 24
- 25
- 26
- 27
- 28
- 29
- 30
- 31
- 32
- 33
- 34
即使用LayoutParams在动画结束后设置下就ok了，这样也能达到属性动画改变view的位置的效果。view 动画＋updateParams 约等于property动画效果。
但是切忌，使用view动画＋updateParams策略时，务必注意不要使用transAnim.setFillAfter(true);这句话，先看看setFillAfter的api：
If fillAfter is true, the transformation that this animation performed will persist when it is finished. Defaults to false if not set. Note that this applies to individual animations and when using an AnimationSet to chain animations.
Related XML Attributes
android:fillAfter
Parameters
fillAfter true if the animation should apply its transformation after it ends
如果为true，动画结束后关于view的变换会一直存在。在view动画＋updateParams＋transAnim.setFillAfter(true)这种策略下，view最终的绘制位置等于将view先updateParams后在新的位置基础上，再进行动画移位，一般情况下这并不是我们想要的！
基本上可以这么说，如果需要view位置真正改变setFillAfter一定不要设！
时间原因，很多东西只有下次再写了，关于属性动画和view动画详细对比可以参考官方文档里How Property Animation Differs from View Animation这一段,见后文。
总之，要知其然并知其所以然，不要一味否定view动画而肯定属性动画。很多多个界面间的复杂效果非view动画不可，用属性动画只能掉坑里，我是两种坑都掉过。如果想改变动画后view的属性，如位置，可以用属性动画也可以用view动画＋updateParams,当然前者更省事。在有些情况下，仅仅是想得到动画的呈现，动画结束后的位置就是view的初始位置，如view从一个地方飞过来，动画结束时view的位置就是view的位置时，此时view动画最合适！
The view animation system provides the capability to only animate View objects, so if you wanted to animate non-View objects, you have to implement your own code to do so. The view animation system is also constrained in the fact that it only exposes a few aspects of a View object to animate, such as the scaling and rotation of a View but not the background color, for instance.
Another disadvantage of the view animation system is that it only modified where the View was drawn, and not the actual View itself. For instance, if you animated a button to move across the screen, the button draws correctly, but the actual location where you can click the button does not change, so you have to implement your own logic to handle this.
With the property animation system, these constraints are completely removed, and you can animate any property of any object (Views and non-Views) and the object itself is actually modified. The property animation system is also more robust in the way it carries out animation. At a high level, you assign animators to the properties that you want to animate, such as color, position, or size and can define aspects of the animation such as interpolation and synchronization of multiple animators.
The view animation system, however, takes less time to setup and requires less code to write. If view animation accomplishes everything that you need to do, or if your existing code already works the way you want, there is no need to use the property animation system. It also might make sense to use both animation systems for different situations if the use case arises.
文中测试代码下载：http://download.csdn.net/detail/yanzi1225627/9034125
－－—–－－本文系原创，转载注明作者yanzi1225627
