之前也写过类似的blog,今天回过头来重新理解了一下,觉得当时很多地方有问题,因此再写一篇,一是纠正自己对android事件分发这块的理解,二是想让更多还不是太了解这方面的人也能够掌握。所以本文用的都是最简单的案例,最有力的说明,来一步步阐述android事件分发机制。
首先要弄清楚View的事件分发,这里会牵扯到几个相关的方法:dispatchTouchEvent、onTouch、onTouchEvent。具体各自都有些什么用处,跟着例子来发现。
分别新建两个类MyButton、MyImage,作为测试之用:
MyButton.java:
package com.cjt.event;
import android.content.Context;
import android.util.AttributeSet;
import android.util.Log;
import android.view.MotionEvent;
import android.view.View;
import android.widget.Button;
/**
* Created by mvp-cjt on 2016/6/14.
* Email:879309896@qq.com
*/
public class MyButton extends Button implements View.OnTouchListener, View.OnClickListener, View.OnLongClickListener{
public final static String TAG = "mvp-cjt";
public MyButton(Context context, AttributeSet attrs) {
super(context, attrs);
setOnTouchListener(this);
setOnClickListener(this);
setOnLongClickListener(this);
}
@Override
public boolean dispatchTouchEvent(MotionEvent ev) {
switch (ev.getAction()){
case MotionEvent.ACTION_DOWN:
Log.i(TAG, "MyButton dispatchTouchEvent: ACTION_DOWN");
break;
case MotionEvent.ACTION_MOVE:
Log.i(TAG, "MyButton dispatchTouchEvent: ACTION_MOVE");
break;
case MotionEvent.ACTION_UP:
Log.i(TAG, "MyButton dispatchTouchEvent: ACTION_UP");
break;
default:
break;
}
return super.dispatchTouchEvent(ev);
}
@Override
public boolean onTouch(View view, MotionEvent ev) {
switch (ev.getAction()){
case MotionEvent.ACTION_DOWN:
Log.i(TAG, "MyButton onTouch: ACTION_DOWN");
break;
case MotionEvent.ACTION_MOVE:
Log.i(TAG, "MyButton onTouch: ACTION_MOVE");
break;
case MotionEvent.ACTION_UP:
Log.i(TAG, "MyButton onTouch: ACTION_UP");
break;
default:
break;
}
return false;
}
@Override
public boolean onTouchEvent(MotionEvent ev) {
switch (ev.getAction()){
case MotionEvent.ACTION_DOWN:
Log.i(TAG, "MyButton onTouchEvent: ACTION_DOWN");
break;
case MotionEvent.ACTION_MOVE:
Log.i(TAG, "MyButton onTouchEvent: ACTION_MOVE");
break;
case MotionEvent.ACTION_UP:
Log.i(TAG, "MyButton onTouchEvent: ACTION_UP");
break;
default:
break;
}
return super.onTouchEvent(ev);
}
@Override
public void onClick(View view) {
Log.i(TAG, "MyButton onClick");
}
@Override
public boolean onLongClick(View view) {
Log.i(TAG, "MyButton onLongClick");
return true;
}
}
MyImage.java:
package com.cjt.event;
import android.content.Context;
import android.util.AttributeSet;
import android.util.Log;
import android.view.MotionEvent;
import android.view.View;
import android.widget.ImageView;
/**
* Created by mvp-cjt on 2016/6/14.
* Email:879309896@qq.com
*/
public class MyImage extends ImageView implements View.OnTouchListener{
public final static String TAG = "mvp-cjt";
public MyImage(Context context, AttributeSet attrs) {
super(context, attrs);
setOnTouchListener(this);
}
@Override
public boolean dispatchTouchEvent(MotionEvent ev) {
switch (ev.getAction()){
case MotionEvent.ACTION_DOWN:
Log.i(TAG, "MyImage dispatchTouchEvent: ACTION_DOWN");
break;
case MotionEvent.ACTION_MOVE:
Log.i(TAG, "MyImage dispatchTouchEvent: ACTION_MOVE");
break;
case MotionEvent.ACTION_UP:
Log.i(TAG, "MyImage dispatchTouchEvent: ACTION_UP");
break;
default:
break;
}
return super.dispatchTouchEvent(ev);
}
@Override
public boolean onTouch(View view, MotionEvent ev) {
switch (ev.getAction()){
case MotionEvent.ACTION_DOWN:
Log.i(TAG, "MyImage onTouch: ACTION_DOWN");
break;
case MotionEvent.ACTION_MOVE:
Log.i(TAG, "MyImage onTouch: ACTION_MOVE");
break;
case MotionEvent.ACTION_UP:
Log.i(TAG, "MyImage onTouch: ACTION_UP");
break;
default:
break;
}
return false;
}
@Override
public boolean onTouchEvent(MotionEvent ev) {
switch (ev.getAction()){
case MotionEvent.ACTION_DOWN:
Log.i(TAG, "MyImage onTouchEvent: ACTION_DOWN");
break;
case MotionEvent.ACTION_MOVE:
Log.i(TAG, "MyImage onTouchEvent: ACTION_MOVE");
break;
case MotionEvent.ACTION_UP:
Log.i(TAG, "MyImage onTouchEvent: ACTION_UP");
break;
default:
break;
}
return super.onTouchEvent(ev);
}
}
主界面相当的简单,就放置这两个控件即可activity__main.xml:
<?xml version="1.0" encoding="utf-8"?>
<RelativeLayout
xmlns:android="http://schemas.android.com/apk/res/android"
android:layout_width="match_parent"
android:layout_height="match_parent">
<com.cjt.event.MyButton
android:id="@+id/my_button"
android:layout_centerInParent="true"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:text="button"/>
<com.cjt.event.MyImage
android:layout_below="@+id/my_button"
android:layout_centerHorizontal="true"
android:src="@mipmap/ic_launcher"
android:layout_width="wrap_content"
android:layout_height="wrap_content"/>
</RelativeLayout>
做个试验,点击一下MyImage:
06-14 23:35:31.032 21139-21139/com.cjt.event I/mvp-cjt: MyImage dispatchTouchEvent: ACTION_DOWN
06-14 23:35:31.032 21139-21139/com.cjt.event I/mvp-cjt: MyImage onTouch: ACTION_DOWN
06-14 23:35:31.032 21139-21139/com.cjt.event I/mvp-cjt: MyImage onTouchEvent: ACTION_DOWN
点击一下MyButton:
06-14 23:36:41.233 21139-21139/com.cjt.event I/mvp-cjt: MyButton dispatchTouchEvent: ACTION_DOWN
06-14 23:36:41.234 21139-21139/com.cjt.event I/mvp-cjt: MyButton onTouch: ACTION_DOWN
06-14 23:36:41.234 21139-21139/com.cjt.event I/mvp-cjt: MyButton onTouchEvent: ACTION_DOWN
06-14 23:36:41.245 21139-21139/com.cjt.event I/mvp-cjt: MyButton dispatchTouchEvent: ACTION_MOVE
06-14 23:36:41.246 21139-21139/com.cjt.event I/mvp-cjt: MyButton onTouch: ACTION_MOVE
06-14 23:36:41.246 21139-21139/com.cjt.event I/mvp-cjt: MyButton onTouchEvent: ACTION_MOVE
06-14 23:36:41.312 21139-21139/com.cjt.event I/mvp-cjt: MyButton dispatchTouchEvent: ACTION_UP
06-14 23:36:41.313 21139-21139/com.cjt.event I/mvp-cjt: MyButton onTouch: ACTION_UP
06-14 23:36:41.313 21139-21139/com.cjt.event I/mvp-cjt: MyButton onTouchEvent: ACTION_UP
由以上两个小试验可以得出:
1. 事件传递顺序dispatchTouchEvent->onTouch->onTouchEvent;
2. MyImage只能触发DOWN事件,而MyButton能够触发一个完整的事件;
那么问题来了,上面试验的具体考证?还有MyImage和MyButton在事件分发中的本质区别?都等着去探究,那么看看dispatchTouchEvent的源码,这里只截取关键部分:
public boolean dispatchTouchEvent(MotionEvent event) {
if (mOnTouchListener != null && mOnTouchListener.onTouch(this, event)) {
// 设置了onTouchListener且onTouch返回true,则屏蔽onTouchEvent方法(performClick)
return true;
}
return onTouchEvent(event);
}
印证了上面的第一条,android事件分发的执行顺序,这里也清楚的说明了onTouch与onTouchEvent之间的关系:若设置了onTouchListener,且onTouch返回值为true,则屏蔽掉onTouchEvent方法,否者执行onTouchEvent。
那上面的第二条呢?不慌,看看onTouchEvent的源码,还是截取关键的部分:
public boolean onTouchEvent(MotionEvent event){
// 可点击或长按
if (((viewFlags & CLICKABLE) == CLICKABLE || (viewFlags & LONG_CLICKABLE) == LONG_CLICKABLE)) {
switch (event.getAction()) {
case MotionEvent.ACTION_UP:
performClick();
...
}
return true;
}
return false;
}
可点击或者长按就会执行performClick(点击、长按事件),并且返回true,否者返回false,难道这就是MyButton和MyImage在事件分发的区别么?在延伸一下,可点击或者长按,最后直接导致dispatchTouchEvent返回true,直接代表是MyButton;否则返回false,直接代表则是MyImage。那么是不是就可以说dispatchTouchEvent在DOWN的时候返回true就代表该View能够触发一个完整的事件,而返回false就只能触发一个DOWN事件呢?
实践是检验真理的唯一标准。修改MyImage.java,设置onTouch返回值为true,这样MyImage.java在DOWN时dispatchTouchEvent返回的是true,点击测试:
06-15 00:02:48.629 21139-21139/com.cjt.event I/mvp-cjt: MyImage dispatchTouchEvent: ACTION_DOWN
06-15 00:02:48.629 21139-21139/com.cjt.event I/mvp-cjt: MyImage onTouch: ACTION_DOWN
06-15 00:02:48.633 21139-21139/com.cjt.event I/mvp-cjt: MyImage dispatchTouchEvent: ACTION_MOVE
06-15 00:02:48.633 21139-21139/com.cjt.event I/mvp-cjt: MyImage onTouch: ACTION_MOVE
06-15 00:02:48.643 21139-21139/com.cjt.event I/mvp-cjt: MyImage dispatchTouchEvent: ACTION_UP
06-15 00:02:48.644 21139-21139/com.cjt.event I/mvp-cjt: MyImage onTouch: ACTION_UP
果然如此,要注意的是这样则屏蔽了onTouchEvent方法,控制台也就不会打印了。
或者说,让MyImage可点击不就可以了么,在构造方法中加一句 setClickable(true),点击测试:
06-15 00:05:25.399 21139-21139/com.cjt.event I/mvp-cjt: MyImage dispatchTouchEvent: ACTION_DOWN
06-15 00:05:25.399 21139-21139/com.cjt.event I/mvp-cjt: MyImage onTouch: ACTION_DOWN
06-15 00:05:25.399 21139-21139/com.cjt.event I/mvp-cjt: MyImage onTouchEvent: ACTION_DOWN
06-15 00:05:25.426 21139-21139/com.cjt.event I/mvp-cjt: MyImage dispatchTouchEvent: ACTION_MOVE
06-15 00:05:25.426 21139-21139/com.cjt.event I/mvp-cjt: MyImage onTouch: ACTION_MOVE
06-15 00:05:25.426 21139-21139/com.cjt.event I/mvp-cjt: MyImage onTouchEvent: ACTION_MOVE
06-15 00:05:25.437 21139-21139/com.cjt.event I/mvp-cjt: MyImage dispatchTouchEvent: ACTION_UP
06-15 00:05:25.437 21139-21139/com.cjt.event I/mvp-cjt: MyImage onTouch: ACTION_UP
06-15 00:05:25.437 21139-21139/com.cjt.event I/mvp-cjt: MyImage onTouchEvent: ACTION_UP
嗯,跟我们预期的是一样的。那么证明上述的小结是正确的。顺势,归纳一下View中的事件分发机制:
1. 事件的传递顺序是dispatchTouchEvent->onTouch->onTouchEvent;
2. dispatchTouchEvent在DOWN的返回值决定了该View能否触发一个完整的事件,决定因素有三:是否设置onTouchListener、onTouch的返回值,onTouchEvent的返回值,而onTouchEvent的返回值又直接被可点击或者长按决定;
花边:当既设置了onClickListener,也设置了onLongClickListener时
1:onLongClickListener.onClick返回true;代表消费掉了下发的事件,onClickListener无法触发
2:onLongClickListener.onClick返回false;代表不消费下发的事件,onClickListener也可以触发