Android触摸事件传递机制

概述 Android触摸事件传递机制 一次完整的事件传递主要包括三个阶段,分别是事件的分发、拦截和消费. 1.1 触摸事件的类型 触摸事件对应的是MotionEvent类,事件的类型主要有如下三种: 　　1>.ACTION_DOWN: 用户手指的按下 *** 作,一个按下 *** 作标志着一次触摸事件的开始. 　　2>.ACTION_MOVE: 用户手指的按压屏幕后,在松开之前,如果移动的距离超过一定的阈(yu)值,  AndroID触摸事件传递机制

一次完整的事件传递主要包括三个阶段,分别是事件的分发、拦截和消费.

1.1 触摸事件的类型

触摸事件对应的是MotionEvent类,事件的类型主要有如下三种:

　　1>.ACTION_DOWN: 用户手指的按下 *** 作,一个按下 *** 作标志着一次触摸事件的开始.

　　2>.ACTION_MOVE: 用户手指的按压屏幕后,在松开之前,如果移动的距离超过一定的阈(yu)值,那么会被判定为ACTION_MOVE *** 作,一般情况下,手指的轻微西东都会触发一系列的移动事件.

　　3>.ACTION_UP: 用户手指离开屏幕的 *** 作,一次抬起 *** 作标志着一次触摸事件的结束.

　　在一次屏幕触摸的 *** 作中,ACTION_DOWN和ACTION_UP这两个事件是必需的,而ACTION_MOVE视情况而定,如果用户仅仅是点击了一下屏幕那么可能只会监测到按下和抬起的动作.

1.2 事件传递的三个阶段 　　1.分发(dispatch)

　　事件的分发对应着dispatchtouchEvent 方法,在AndroID系统中,所有的触摸事件都是通过这个方法来分发的,

　　

 public boolean dispatchtouchEvent(MotionEvent ev) {        return super.dispatchtouchEvent(ev);    }

该方法返回true表示事件被当前视图消费掉,不再继续分发事件;方法返回super.dispatchtouchEvent(ev) 表示继续分发该事件.

如果当前视图是VIEwGroup及其子类,则回调用onIntercepttouchEvent方法判定是否拦截该事件.

 

　　2.拦截(Intercept)

　　事件的拦截对应着onIntercepttouchEvent方法,这个方法只在VIEwGroup及其子类才存在,在VIEw和Activity中不存在的.

　　

 public boolean onIntercepttouchEvent(MotionEvent ev) {        return super.onIntercepttouchEvent(ev);    }

该方法返回true表示拦截这个事件,不在继续分发给子视图,同时交由自身的ontouchEvent方法进行消费;返回false和super.onIntercepttouchEvent(ev)表示不对事件进行拦截,需要继续传给子视图.

 

　　3.消费(Consume)

　　事件的消费对应着ontouchEvent 方法

public boolean ontouchEvent(MotionEvent event) {        return super.ontouchEvent(event);    }

该方法返回值为true表示当前视图可以处理对应的事件,事件将不会向上传递给父视图;返回值为false表示当前的视图不处理这个事件,事件会被传递给父视图的ontouchEvent方法进行处理.

 

在AndroID系统中,拥有事件传递处理能力的类有一下三种:

　　1>.Activity: 拥有dispatchtouchEvent 和 ontouchEvent 两种方法.

　　2>.VIEwGroup: 拥有dispatchtouchEvent 、onIntercepttouchEvent和 ontouchEvent 三种方法.

　　3>.VIEw: 拥有dispatchtouchEvent 和 ontouchEvent 两种方法.

1.3 VIEw的事件传递机制

　　VIEw控件拥有dispatchtouchEvent 和 ontouchEvent 两种方法,定义一个继承TextVIEw的类和MyTextVIEw,如下所示:我们将每个事件的触发事件都打上Log,以方便了解事件的传递流程.

public class MyTextVIEw extends TextVIEw {    private static final String TAG ="MyTextVIEw";    public MyTextVIEw(Context context) {        super(context);    }    public MyTextVIEw(Context context,AttributeSet attrs) {        super(context,attrs);    }    @OverrIDe    public boolean dispatchtouchEvent(MotionEvent event) {        switch (event.getAction()){            case MotionEvent.ACTION_DOWN:                Log.e(TAG,"dispatchtouchEvent: ACTION_DOWN");                break;            case MotionEvent.ACTION_MOVE:                Log.e(TAG,"dispatchtouchEvent: ACTION_MOVE");                break;            case MotionEvent.ACTION_UP:                Log.e(TAG,"dispatchtouchEvent: ACTION_UP");                break;            case MotionEvent.ACTION_CANCEL:                Log.e(TAG,"dispatchtouchEvent: ACTION_CANCEL");                break;            default:                break;        }        return super.dispatchtouchEvent(event);    }    @OverrIDe    public boolean ontouchEvent(MotionEvent event) {        switch (event.getAction()){            case MotionEvent.ACTION_DOWN:                Log.e(TAG,"ontouchEvent: ACTION_DOWN");                break;            case MotionEvent.ACTION_MOVE:                Log.e(TAG,"ontouchEvent: ACTION_MOVE");                break;            case MotionEvent.ACTION_UP:                Log.e(TAG,"ontouchEvent: ACTION_UP");                break;            case MotionEvent.ACTION_CANCEL:                Log.e(TAG,"ontouchEvent: ACTION_CANCEL");                break;            default:                break;        }        return super.ontouchEvent(event);    }}

 

同时定义一个MainActivity用来展示MyTextVIEw,在这个Activity中,为MyTextVIEw设置了点击(onClick)和触摸(ontouch)监听,方便跟踪了解事件传递的流程:

public class MainActivity extends AppCompatActivity implements VIEw.OnClickListener,VIEw.OntouchListener {    private static final String TAG ="MainActivity";    private MyTextVIEw mTextVIEw;    @OverrIDe    protected voID onCreate(Bundle savedInstanceState) {        super.onCreate(savedInstanceState);        setContentVIEw(R.layout.activity_main);        mTextVIEw =findVIEwByID(R.ID.my_text);        mTextVIEw.setonClickListener(this);        mTextVIEw.setontouchListener(this);    }    @OverrIDe    public boolean dispatchtouchEvent(MotionEvent ev) {        switch (ev.getAction()){            case MotionEvent.ACTION_DOWN:                Log.e(TAG,"dispatchtouchEvent: ACTION_CANCEL");                break;            default:                break;        }        return super.dispatchtouchEvent(ev);    }    @OverrIDe    public boolean ontouch(VIEw v,MotionEvent event) {        switch (v.getID()) {            case R.ID.my_text:                switch (event.getAction()) {                    case MotionEvent.ACTION_DOWN:                        Log.e(TAG,"MyTextVIEw ontouch: ACTION_DOWN");                        break;                    case MotionEvent.ACTION_MOVE:                        Log.e(TAG,"MyTextVIEw ontouch: ACTION_MOVE");                        break;                    case MotionEvent.ACTION_UP:                        Log.e(TAG,"MyTextVIEw ontouch: ACTION_UP");                        break;                    case MotionEvent.ACTION_CANCEL:                        Log.e(TAG,"MyTextVIEw ontouch: ACTION_CANCEL");                        break;                    default:                        break;                }                break;            default:                break;        }        return false;    }    @OverrIDe    public voID onClick(VIEw v) {        switch (v.getID()){            case R.ID.my_text:                Log.e(TAG,"MyTextVIEw onClick: ");                break;            default:                break;        }    }}

运行上面的代码,点击MyTextVIEw,在Logcat中将打印如下日志:

09-02 20:25:01.783 15374-15374/com.kitking.androIDtest E/MainActivity: dispatchtouchEvent: ACTION_DOWN09-02 20:25:01.783 15374-15374/com.kitking.androIDtest E/MyTextVIEw: dispatchtouchEvent: ACTION_DOWN09-02 20:25:01.783 15374-15374/com.kitking.androIDtest E/MainActivity: MyTextVIEw ontouch: ACTION_DOWN09-02 20:25:01.783 15374-15374/com.kitking.androIDtest E/MyTextVIEw: ontouchEvent: ACTION_DOWN09-02 20:25:01.833 15374-15374/com.kitking.androIDtest E/MainActivity: dispatchtouchEvent: ACTION_UP09-02 20:25:01.843 15374-15374/com.kitking.androIDtest E/MyTextVIEw: dispatchtouchEvent: ACTION_UP09-02 20:25:01.843 15374-15374/com.kitking.androIDtest E/MainActivity: MyTextVIEw ontouch: ACTION_UP09-02 20:25:01.843 15374-15374/com.kitking.androIDtest E/MyTextVIEw: ontouchEvent: ACTION_UP09-02 20:25:01.843 15374-15374/com.kitking.androIDtest E/MainActivity: MyTextVIEw onClick: 

按下按压抬起MyTextVIEw,在Logcat中将打印如下日志:

09-02 20:33:50.583 15374-15374/com.kitking.androIDtest E/MainActivity: dispatchtouchEvent: ACTION_DOWN09-02 20:33:50.583 15374-15374/com.kitking.androIDtest E/MyTextVIEw: dispatchtouchEvent: ACTION_DOWN09-02 20:33:50.583 15374-15374/com.kitking.androIDtest E/MainActivity: MyTextVIEw ontouch: ACTION_DOWN09-02 20:33:50.583 15374-15374/com.kitking.androIDtest E/MyTextVIEw: ontouchEvent: ACTION_DOWN09-02 20:33:50.643 15374-15374/com.kitking.androIDtest E/MainActivity: dispatchtouchEvent: ACTION_MOVE09-02 20:33:50.643 15374-15374/com.kitking.androIDtest E/MyTextVIEw: dispatchtouchEvent: ACTION_MOVE09-02 20:33:50.643 15374-15374/com.kitking.androIDtest E/MainActivity: MyTextVIEw ontouch: ACTION_MOVE09-02 20:33:50.643 15374-15374/com.kitking.androIDtest E/MyTextVIEw: ontouchEvent: ACTION_MOVE09-02 20:33:50.673 15374-15374/com.kitking.androIDtest E/MainActivity: dispatchtouchEvent: ACTION_MOVE09-02 20:33:50.673 15374-15374/com.kitking.androIDtest E/MyTextVIEw: dispatchtouchEvent: ACTION_MOVE09-02 20:33:50.673 15374-15374/com.kitking.androIDtest E/MainActivity: MyTextVIEw ontouch: ACTION_MOVE09-02 20:33:50.673 15374-15374/com.kitking.androIDtest E/MyTextVIEw: ontouchEvent: ACTION_MOVE09-02 20:33:51.173 15374-15374/com.kitking.androIDtest E/MainActivity: dispatchtouchEvent: ACTION_MOVE09-02 20:33:51.173 15374-15374/com.kitking.androIDtest E/MyTextVIEw: dispatchtouchEvent: ACTION_MOVE09-02 20:33:51.173 15374-15374/com.kitking.androIDtest E/MainActivity: MyTextVIEw ontouch: ACTION_MOVE09-02 20:33:51.173 15374-15374/com.kitking.androIDtest E/MyTextVIEw: ontouchEvent: ACTION_MOVE09-02 20:33:51.173 15374-15374/com.kitking.androIDtest E/MainActivity: dispatchtouchEvent: ACTION_UP09-02 20:33:51.183 15374-15374/com.kitking.androIDtest E/MyTextVIEw: dispatchtouchEvent: ACTION_UP09-02 20:33:51.183 15374-15374/com.kitking.androIDtest E/MainActivity: MyTextVIEw ontouch: ACTION_UP09-02 20:33:51.183 15374-15374/com.kitking.androIDtest E/MyTextVIEw: ontouchEvent: ACTION_UP09-02 20:33:51.183 15374-15374/com.kitking.androIDtest E/MainActivity: MyTextVIEw onClick: 

从上面的运行的日志可以看出,dispatchtouchEvent、ontouchEvent这两个方法的返回值存在三种情况:

　　1>. return false;

　　　　

09-02 20:46:38.013 21590-21590/com.kitking.androIDtest E/MainActivity: dispatchtouchEvent: ACTION_DOWN09-02 20:46:38.103 21590-21590/com.kitking.androIDtest E/MainActivity: dispatchtouchEvent: ACTION_UP

 

　　2>. return true;

09-02 20:45:23.733 20676-20676/com.kitking.androIDtest E/MainActivity: dispatchtouchEvent: ACTION_DOWN09-02 20:45:23.753 20676-20676/com.kitking.androIDtest E/MainActivity: dispatchtouchEvent: ACTION_UP

　　3>. 返回父类的同名方法 return super.dispatchtouchEvent(ev);

　　

09-02 20:25:01.783 15374-15374/com.kitking.androIDtest E/MainActivity: dispatchtouchEvent: ACTION_DOWN09-02 20:25:01.783 15374-15374/com.kitking.androIDtest E/MyTextVIEw: dispatchtouchEvent: ACTION_DOWN09-02 20:25:01.783 15374-15374/com.kitking.androIDtest E/MainActivity: MyTextVIEw ontouch: ACTION_DOWN09-02 20:25:01.783 15374-15374/com.kitking.androIDtest E/MyTextVIEw: ontouchEvent: ACTION_DOWN09-02 20:25:01.833 15374-15374/com.kitking.androIDtest E/MainActivity: dispatchtouchEvent: ACTION_UP09-02 20:25:01.843 15374-15374/com.kitking.androIDtest E/MyTextVIEw: dispatchtouchEvent: ACTION_UP09-02 20:25:01.843 15374-15374/com.kitking.androIDtest E/MainActivity: MyTextVIEw ontouch: ACTION_UP09-02 20:25:01.843 15374-15374/com.kitking.androIDtest E/MyTextVIEw: ontouchEvent: ACTION_UP09-02 20:25:01.843 15374-15374/com.kitking.androIDtest E/MainActivity: MyTextVIEw onClick: 

 

不同的返回值会导致事件的传递流程相差甚远,通过不断的修改这些方法的返回值查看日志的记录;可以得出以下结论:

 1>. 触摸事件的传递流程是从dispatchtouchEvent开始的,如果不进行人为干预(也就是说默认返回父类的同名函数),则事件将会依照嵌套层向外层传递,到达最内层的VIEw时,就由它的ontouchEvent 方法处理,

　　则返回的true,如果处理不了,怎返回false,这时事件会重新向外层传递,并由外层的VIEw的ontouchEvent方法进行处理,以此类推.

2>. 如果事件在向内层传递过程中由于人为干预,事件处理函数返回true,则会导致事件提前被消费,内层VIEw将不会收到这个事件.

3>. VIEw控件的事件触发顺序是先执行ontouch 方法,在最后才执行 onClick方法. 如果ontouch 返回true,则事件不会继续传递,最后也不会调用onClick方法;如果ontouch返回false,则事件继续传递.

 

 

 

1.4. VIEwGroup的事件传递机制

VIEwGroup拥有dispatchtouchEvent 、onIntercepttouchEvent和 ontouchEvent 三种方法.

可以看出和VIEw的唯一的区别是多了一个onIntercepttouchEvent方法;演示,我们定义如下一个VIEwGroup,继承relativeLayout,实现一个MyrelativeLayout .

public class MyrelativeLayout extends relativeLayout {    private static final String TAG ="MyrelativeLayout";    public MyrelativeLayout(Context context) {        super(context);    }    public MyrelativeLayout(Context context,"dispatchtouchEvent: ACTION_CANCEL");                break;            default:                break;        }        return super.dispatchtouchEvent(event);    }    @OverrIDe    public boolean onIntercepttouchEvent(MotionEvent event) {        switch (event.getAction()){            case MotionEvent.ACTION_DOWN:                Log.e(TAG,"onIntercepttouchEvent: ACTION_DOWN");                break;            case MotionEvent.ACTION_MOVE:                Log.e(TAG,"onIntercepttouchEvent: ACTION_MOVE");                break;            case MotionEvent.ACTION_UP:                Log.e(TAG,"onIntercepttouchEvent: ACTION_UP");                break;            case MotionEvent.ACTION_CANCEL:                Log.e(TAG,"onIntercepttouchEvent: ACTION_CANCEL");                break;            default:                break;        }        return super.onIntercepttouchEvent(event);    }    @OverrIDe    public boolean ontouchEvent(MotionEvent event) {        switch (event.getAction()){            case MotionEvent.ACTION_DOWN:                Log.e(TAG,"ontouchEvent: ACTION_CANCEL");                break;            default:                break;        }        return super.ontouchEvent(event);    }}

<?xml version="1.0" enCoding="utf-8"?><com.kitking.androIDtest.event.MyrelativeLayout    xmlns:androID="http://schemas.androID.com/apk/res/androID"    androID:layout_wIDth="match_parent"    androID:layout_height="match_parent">    <com.kitking.androIDtest.event.MyTextVIEw        androID:ID="@+ID/my_text"        androID:layout_wIDth="wrap_content"        androID:layout_height="wrap_content"        androID:textSize="30dp"        androID:text="Event"/></com.kitking.androIDtest.event.MyrelativeLayout>

运行,在Logcat中打印日志如下:

09-02 21:01:07.813 25884-25884/com.kitking.androIDtest E/MainActivity: dispatchtouchEvent: ACTION_DOWN09-02 21:01:07.823 25884-25884/com.kitking.androIDtest E/MyrelativeLayout: dispatchtouchEvent: ACTION_DOWN09-02 21:01:07.823 25884-25884/com.kitking.androIDtest E/MyrelativeLayout: onIntercepttouchEvent: ACTION_DOWN09-02 21:01:07.823 25884-25884/com.kitking.androIDtest E/MyTextVIEw: dispatchtouchEvent: ACTION_DOWN09-02 21:01:07.823 25884-25884/com.kitking.androIDtest E/MainActivity: MyTextVIEw ontouch: ACTION_DOWN09-02 21:01:07.823 25884-25884/com.kitking.androIDtest E/MyTextVIEw: ontouchEvent: ACTION_DOWN09-02 21:01:07.833 25884-25884/com.kitking.androIDtest E/MainActivity: dispatchtouchEvent: ACTION_UP09-02 21:01:07.833 25884-25884/com.kitking.androIDtest E/MyrelativeLayout: dispatchtouchEvent: ACTION_UP09-02 21:01:07.833 25884-25884/com.kitking.androIDtest E/MyrelativeLayout: onIntercepttouchEvent: ACTION_UP09-02 21:01:07.833 25884-25884/com.kitking.androIDtest E/MyTextVIEw: dispatchtouchEvent: ACTION_UP09-02 21:01:07.833 25884-25884/com.kitking.androIDtest E/MainActivity: MyTextVIEw ontouch: ACTION_UP09-02 21:01:07.833 25884-25884/com.kitking.androIDtest E/MyTextVIEw: ontouchEvent: ACTION_UP09-02 21:01:07.853 25884-25884/com.kitking.androIDtest E/MainActivity: MyTextVIEw onClick: 

可以看到,与VIEw的事件流程唯一不一样的地方是在MainActivity和MyTextVIEw之间增加了MyrelativeLayout,同理通过打印日志可以获得以下结论:

1>. 触摸事件的传递顺序由Activity到VIEwGroup,在由VIEwGroup传递给它的子类VIEw

2>. VIEwGroup通过dispatchtouchEvent方法对事件进行拦截,如果该方法返回true,则事件不会继续传给子VIEw,如果返回false或者super.dispatchtouchEvent,则事件会继续传递给子VIEw.

3>. 在子VIEw对事件进行消费后,VIEwGroup将接收不到任何事件.

总结

以上是内存溢出为你收集整理的Android触摸事件传递机制全部内容，希望文章能够帮你解决Android触摸事件传递机制所遇到的程序开发问题。

如果觉得内存溢出网站内容还不错，欢迎将内存溢出网站推荐给程序员好友。