android touch事件分发机制的探究

最新推荐文章于 2019-10-20 00:02:59 发布
最新推荐文章于 2019-10-20 00:02:59 发布
阅读量563 收藏
点赞数
分类专栏： android 文章标签： android
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/y1962475006/article/details/52150564
版权

android touch事件分发机制的探究

首先有个认知：
view、viewGroup、各种layout之间的关系：
viewGroup是view的子类，layout是viewGroup的子类。
自定义viewGroup必须要重写onLayout（）；自定义view无法重写onInterceptTouchEvent

自己做了个简单demo，用来研究touch的分发机制。先把代码贴出来：

layout文件

<?xml version="1.0" encoding="utf-8"?>
<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
    android:orientation="vertical"
    android:layout_width="match_parent"
    android:layout_height="match_parent"
    android:id="@+id/root"
    >

    <android.crm.paic.com.yueshaojun.view.Parent
        android:id="@+id/parent"
        android:layout_width="300dp"
        android:layout_height="400dp"
        android:background="#1E90FF"
        >
        <android.crm.paic.com.yueshaojun.view.ParentTwo
            android:layout_alignParentTop="true"
            android:id = "@+id/parentTwo"
            android:background="#FFC0CB"
            android:layout_width="250dp"
            android:layout_height="250dp">
            <android.crm.paic.com.yueshaojun.view.Child
                android:id="@+id/child1"
                android:background="#8B008B"
                android:layout_width="100dp"
                android:layout_alignParentStart="true"
                android:layout_height="100dp">
            </android.crm.paic.com.yueshaojun.view.Child>
            <android.crm.paic.com.yueshaojun.view.Child
                android:id="@+id/child2"
                android:background="#BA55D3"
                android:layout_width="100dp"
                android:layout_alignParentEnd="true"
                android:layout_height="100dp">
                </android.crm.paic.com.yueshaojun.view.Child>
        </android.crm.paic.com.yueshaojun.view.ParentTwo>
    </android.crm.paic.com.yueshaojun.view.Parent>
</LinearLayout>

parent视图类：

package android.crm.paic.com.yueshaojun.view;

import android.content.Context;
import android.crm.paic.com.yueshaojun.utils.Tools;
import android.util.AttributeSet;
import android.util.Log;
import android.view.MotionEvent;
import android.widget.LinearLayout;
import android.widget.RelativeLayout;

/**
 * Created by yueshaojun on 16/7/28.
 */
public class Parent extends RelativeLayout {
    public Parent(Context context, AttributeSet attrs) {
        super(context, attrs);
    }

    public Parent(Context context) {
        super(context);
    }

    public Parent(Context context, AttributeSet attrs, int defStyleAttr) {
        super(context, attrs, defStyleAttr);
    }

    @Override
    protected void onMeasure(int widthMeasureSpec, int heightMeasureSpec) {
        super.onMeasure(widthMeasureSpec, heightMeasureSpec);
    }

    @Override
    protected void onLayout(boolean changed, int l, int t, int r, int b) {
        super.onLayout(changed, l, t, r, b);
    }

    @Override
    public boolean onTouchEvent(MotionEvent event) {
        Log.i("ondispatch","parent onTouchEvent---->"+ Tools.getView(getId()));
        switch (event.getAction()){
            case MotionEvent.ACTION_DOWN:
                Log.i("dispatched","parent onTouchEvent---->action_down------>"+ Tools.getView(getId()));
                break;
            case MotionEvent.ACTION_MOVE:
                Log.i("dispatched","parent onTouchEvent---->action_move------>"+ Tools.getView(getId()));
                break;
            case MotionEvent.ACTION_UP:
                Log.i("dispatched","parent onTouchEvent---->action_up------>"+ Tools.getView(getId()));
                break;
        }
        return super.onTouchEvent(event);
    }

    @Override
    public boolean dispatchTouchEvent(MotionEvent ev) {
        Log.i("ondispatch","parent dispatchTouchEvent---->"+Tools.getView(getId()));
        switch (ev.getAction()){
            case MotionEvent.ACTION_DOWN:
                Log.i("dispatched","parent dispatchTouchEvent---->action_down------>"+ Tools.getView(getId()));
                break;
            case MotionEvent.ACTION_MOVE:
                Log.i("dispatched","parent dispatchTouchEvent---->action_move------>"+ ev.getRawY()+"||"+ Tools.getView(getId()));
                break;
            case MotionEvent.ACTION_UP:
                Log.i("dispatched","parent dispatchTouchEvent---->action_up------>"+ Tools.getView(getId()));
                break;
        }
        return super.dispatchTouchEvent(ev);
    }

    @Override
    public boolean onInterceptTouchEvent(MotionEvent ev) {
        Log.i("ondispatch","parent onInterceptTouchEvent---->"+Tools.getView(getId()));
        switch (ev.getAction()){
            case MotionEvent.ACTION_DOWN:
                Log.i("dispatched","parent onInterceptTouchEvent---->action_down------>"+ Tools.getView(getId()));
                break;
            case MotionEvent.ACTION_MOVE:
                Log.i("dispatched","parent onInterceptTouchEvent---->action_move------>"+ ev.getRawY()+"||"+Tools.getView(getId()));
                break;
            case MotionEvent.ACTION_UP:
                Log.i("dispatched","parent onInterceptTouchEvent---->action_up------>"+ Tools.getView(getId()));
                break;
        }
        return super.onInterceptTouchEvent(ev);
    }
}

parentTwo（中间那层视图）

package android.crm.paic.com.yueshaojun.view;

import android.content.Context;
import android.crm.paic.com.yueshaojun.utils.Tools;
import android.util.AttributeSet;
import android.util.Log;
import android.view.MotionEvent;
import android.widget.LinearLayout;
import android.widget.RelativeLayout;

/**
 * Created by yueshaojun on 16/7/28.
 */
public class ParentTwo extends RelativeLayout {
    public ParentTwo(Context context, AttributeSet attrs) {
        super(context, attrs);
    }

    public ParentTwo(Context context) {
        super(context);
    }

    public ParentTwo(Context context, AttributeSet attrs, int defStyleAttr) {
        super(context, attrs, defStyleAttr);
    }

    @Override
    protected void onMeasure(int widthMeasureSpec, int heightMeasureSpec) {
        super.onMeasure(widthMeasureSpec, heightMeasureSpec);
    }

    @Override
    protected void onLayout(boolean changed, int l, int t, int r, int b) {
        super.onLayout(changed, l, t, r, b);
    }

    @Override
    public boolean onTouchEvent(MotionEvent event) {
        Log.i("ondispatch","parentTwo onTouchEvent---->"+ Tools.getView(getId()));
        switch (event.getAction()){
            case MotionEvent.ACTION_DOWN:
                Log.i("dispatched","parentTwo onTouchEvent---->action_down------>"+ Tools.getView(getId()));
                break;
            case MotionEvent.ACTION_MOVE:
                Log.i("dispatched","parentTwo onTouchEvent---->action_move------>"+ Tools.getView(getId()));
                break;
            case MotionEvent.ACTION_UP:
                Log.i("dispatched","parentTwo onTouchEvent---->action_up------>"+ Tools.getView(getId()));
                break;
        }
         return super.onTouchEvent(event);
    }

    @Override
    public boolean dispatchTouchEvent(MotionEvent ev) {
        Log.i("ondispatch","parentTwo dispatchTouchEvent---->"+Tools.getView(getId()));
        switch (ev.getAction()){
            case MotionEvent.ACTION_DOWN:
                Log.i("dispatched","parentTwo dispatchTouchEvent---->action_down------>"+ Tools.getView(getId()));
                break;
            case MotionEvent.ACTION_MOVE:
                Log.i("dispatched","parentTwo dispatchTouchEvent---->action_move------>"+ ev.getRawY()+"||"+Tools.getView(getId()));
                break;
            case MotionEvent.ACTION_UP:
                Log.i("dispatched","parentTwo dispatchTouchEvent---->action_up------>"+ Tools.getView(getId()));
                break;
        }
        return super.dispatchTouchEvent(ev);
    }

    @Override
    public boolean onInterceptTouchEvent(MotionEvent ev) {
        Log.i("ondispatch","parentTwo onInterceptTouchEvent---->"+Tools.getView(getId()));
        switch (ev.getAction()){
            case MotionEvent.ACTION_DOWN:
                Log.i("dispatched","parentTwo onInterceptTouchEvent---->action_down------>"+ Tools.getView(getId()));
                break;
            case MotionEvent.ACTION_MOVE:
                Log.i("dispatched","parentTwo onInterceptTouchEvent---->action_move------>"+ Tools.getView(getId()));
                break;
            case MotionEvent.ACTION_UP:
                Log.i("dispatched","parentTwo onInterceptTouchEvent---->action_up------>"+ Tools.getView(getId()));
                break;
        }
        return super.onInterceptTouchEvent(ev);
    }
}

最子视图类：

package android.crm.paic.com.yueshaojun.view;

import android.content.Context;
import android.crm.paic.com.yueshaojun.utils.Tools;
import android.util.AttributeSet;
import android.util.Log;
import android.view.MotionEvent;
import android.view.View;

/**
 * Created by yueshaojun on 16/7/28.
 */
public class Child extends View {
    public Child(Context context) {
        super(context);
    }

    public Child(Context context, AttributeSet attrs) {
        super(context, attrs);
    }

    @Override
    public boolean onTouchEvent(MotionEvent event) {
        Log.i("ondispatch", "child onTouchEvent---->"+ Tools.getView(getId()));
        switch (event.getAction()){
            case MotionEvent.ACTION_DOWN:
                Log.i("dispatched","child onTouchEvent---->action_down------>"+ Tools.getView(getId()));
                break;
            case MotionEvent.ACTION_MOVE:
                Log.i("dispatched","child onTouchEvent---->action_move------>"+ Tools.getView(getId()));
                break;
            case MotionEvent.ACTION_UP:
                Log.i("dispatched","child onTouchEvent---->action_up------>"+ Tools.getView(getId()));
                break;
        }
        return super.onTouchEvent(event);
    }

    @Override
    public boolean dispatchTouchEvent(MotionEvent event) {
        Log.i("ondispatch","child dispatchTouchEvent---->"+Tools.getView(getId()));
        switch (event.getAction()){
            case MotionEvent.ACTION_DOWN:
                Log.i("dispatched","child dispatchTouchEvent---->action_down------>"+ Tools.getView(getId()));
                break;
            case MotionEvent.ACTION_MOVE:
                Log.i("dispatched","child dispatchTouchEvent---->action_move------>"+ Tools.getView(getId()));
                break;
            case MotionEvent.ACTION_UP:
                Log.i("dispatched","child dispatchTouchEvent---->action_up------>"+ Tools.getView(getId()));
                break;
        }
        return super.dispatchTouchEvent(event);
    }

}

上面的代码没什么特别的，只是打了日志，方便继续看下面的内容。ondispatch标签是进到乐哪个方法中，dispatched标签是打出具体的事件。视图结构如下：
视图结构

话不多说，直接从现象分析：
一、
什么都没做：

I/ondispatch: parent dispatchTouchEvent—->parent
I/ondispatch: parent onInterceptTouchEvent—->parent
I/ondispatch: parentTwo dispatchTouchEvent—->parentTwo
I/ondispatch: parentTwo onInterceptTouchEvent—->parentTwo
I/ondispatch: child dispatchTouchEvent—->child1
I/ondispatch: child onTouchEvent—->child1
I/ondispatch: parentTwo onTouchEvent—->parentTwo
I/ondispatch: parent onTouchEvent—->parent

首先是一个调用顺序：dispatchTouchEvent——>onInterceptEvent——>onTouchEvent，
然后是父视图和子视图的调用关系：在父视图中调用dispatchTouchEvent、onInterceptTouchEvent，然后分发给子视图去调用onTouchEvent，如果子视图不处理，方向反转，依次调用父视图的onTouchEvent，直到根视图。
来个图：
什么都不做
这么看应该会清晰很多。由dispatchTouchEvent向下分发，onInterceptTouchEvent拦截分发，最后分发给最子视图。处于最子视图并不需要重写dispatchTouchEvent。

然而当查看具体的事件传递的情况时，日志：

I/dispatched: parent dispatchTouchEvent—->action_down——>parent
I/dispatched: parent onInterceptTouchEvent—->action_down——>parent
I/dispatched: parentTwo dispatchTouchEvent—->action_down——>parentTwo
I/dispatched: parentTwo onInterceptTouchEvent—->action_down——>parentTwo
I/dispatched: child dispatchTouchEvent—->action_down——>child1
I/dispatched: child onTouchEvent—->action_down——>child1
I/dispatched: parentTwo onTouchEvent—->action_down——>parentTwo
I/dispatched: parent onTouchEvent—->action_down——>parent
可以看到只有down事件，没有move、up等事件。也就是说，并不知道要交给谁处理。

于是在activity里给child添加点击事件，并且为了完整的看到事件的走向，在activity中也把dispatchTouchEvent、onTouchEvent打出日志，贴一下代码：

public class TouchActivity extends AppCompatActivity implements View.OnClickListener{

    @Override
    protected void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);
        setContentView(R.layout.touch);
        Child child1 = (Child) findViewById(R.id.child1);
        Child child2 = (Child) findViewById(R.id.child2);
        child1.setOnClickListener(this);
        child2.setOnClickListener(this);

    }

    @Override
    public void onClick(View v) {
        switch (v.getId()){
            case R.id.child1:
                Log.i("TouchActivity","child1");
                break;
            case R.id.child2:
                Log.i("TouchActivity","child2");
                break;
        }
    }

    @Override
    public boolean onTouchEvent(MotionEvent event) {

        Log.i("ondispatch","activity onTouchEvent---->");
        switch (event.getAction()){
            case MotionEvent.ACTION_DOWN:
                Log.i("dispatched","activity onTouchEvent---->action_down------>");
                break;
            case MotionEvent.ACTION_MOVE:
                Log.i("dispatched","activity onTouchEvent---->action_move------>");
                break;
            case MotionEvent.ACTION_UP:
                Log.i("dispatched","activity onTouchEvent---->action_up------>");
                break;
        }
        return super.onTouchEvent(event);
    }

    @Override
    public boolean dispatchTouchEvent(MotionEvent ev) {
        Log.i("ondispatch","activity dispatchTouchEvent---->");
        switch (ev.getAction()){
            case MotionEvent.ACTION_DOWN:
                Log.i("dispatched","activity dispatchTouchEvent---->action_down------>");
                break;
            case MotionEvent.ACTION_MOVE:
                Log.i("dispatched","activity dispatchTouchEvent---->action_move------>");
                break;
            case MotionEvent.ACTION_UP:
                Log.i("dispatched","activity dispatchTouchEvent---->action_up------>");
                break;
        }
        return super.dispatchTouchEvent(ev);
    }
}

点击child1。
再来看ondispatch日志标签的内容：

I/ondispatch: activity dispatchTouchEvent—->
I/ondispatch: parent dispatchTouchEvent—->parent
I/ondispatch: parent onInterceptTouchEvent—->parent
I/ondispatch: parentTwo dispatchTouchEvent—->parentTwo
I/ondispatch: parentTwo onInterceptTouchEvent—->parentTwo
I/ondispatch: child dispatchTouchEvent—->child1
I/ondispatch: child onTouchEvent—->child1
I/ondispatch: activity dispatchTouchEvent—->
I/ondispatch: parent dispatchTouchEvent—->parent
I/ondispatch: parent onInterceptTouchEvent—->parent
I/ondispatch: parentTwo dispatchTouchEvent—->parentTwo
I/ondispatch: parentTwo onInterceptTouchEvent—->parentTwo
I/ondispatch: child dispatchTouchEvent—->child1
I/ondispatch: child onTouchEvent—->child1
I/ondispatch: activity dispatchTouchEvent—->
I/ondispatch: parent dispatchTouchEvent—->parent
I/ondispatch: parent onInterceptTouchEvent—->parent
I/ondispatch: parentTwo dispatchTouchEvent—->parentTwo
I/ondispatch: parentTwo onInterceptTouchEvent—->parentTwo
I/ondispatch: child dispatchTouchEvent—->child1
I/ondispatch: child onTouchEvent—->child1
I/ondispatch: activity dispatchTouchEvent—->
I/ondispatch: parent dispatchTouchEvent—->parent
I/ondispatch: parent onInterceptTouchEvent—->parent
I/ondispatch: parentTwo dispatchTouchEvent—->parentTwo
I/ondispatch: parentTwo onInterceptTouchEvent—->parentTwo
I/ondispatch: child dispatchTouchEvent—->child1
I/ondispatch: child onTouchEvent—->child1
I/ondispatch: activity dispatchTouchEvent—->
I/ondispatch: parent dispatchTouchEvent—->parent
I/ondispatch: parent onInterceptTouchEvent—->parent
I/ondispatch: parentTwo dispatchTouchEvent—->parentTwo
I/ondispatch: parentTwo onInterceptTouchEvent—->parentTwo
I/ondispatch: child dispatchTouchEvent—->child1
I/ondispatch: child onTouchEvent—->child1

dispatched日志标签的内容：

I/dispatched: activity dispatchTouchEvent—->action_down——>
I/dispatched: parent dispatchTouchEvent—->action_down——>parent
I/dispatched: parent onInterceptTouchEvent—->action_down——>parent
I/dispatched: parentTwo dispatchTouchEvent—->action_down——>parentTwo
I/dispatched: parentTwo onInterceptTouchEvent—->action_down——>parentTwo
I/dispatched: child dispatchTouchEvent—->action_down——>child1
I/dispatched: child onTouchEvent—->action_down——>child1
I/dispatched: activity dispatchTouchEvent—->action_move——>
I/dispatched: parent dispatchTouchEvent—->action_move——>parent
I/dispatched: parent onInterceptTouchEvent—->action_move——>parent
I/dispatched: parentTwo dispatchTouchEvent—->action_move——>parentTwo
I/dispatched: parentTwo onInterceptTouchEvent—->action_move——>parentTwo
I/dispatched: child dispatchTouchEvent—->action_move——>child1
I/dispatched: child onTouchEvent—->action_move——>child1
I/dispatched: activity dispatchTouchEvent—->action_up——>
I/dispatched: parent dispatchTouchEvent—->action_up——>parent
I/dispatched: parent onInterceptTouchEvent—->action_up——>parent
I/dispatched: parentTwo dispatchTouchEvent—->action_up——>parentTwo
I/dispatched: parentTwo onInterceptTouchEvent—->action_up——>parentTwo
I/dispatched: child dispatchTouchEvent—->action_up——>child1
I/dispatched: child onTouchEvent—->action_up——>child1

对比上面的日志，捋一下过程：

down事件由activity的dispatchTouchEvent－－》parent的dispatchTouchEvent、onInterceptTouchEvent－－》parentTwo的dispatchTouchEvent、onInterceptTouchEvent－－》child1的dispatchTouchEvent、onTouchEvent
然后其他事件如move、up再沿着down的路径分发，直到child1最后的onTouchEvent。
另外这说明了，事件分发的起点是activity。

二、
dispatchTouchEvent、onInterceptTouchEvent、onTouchEvent返回值有三种：true、false、super.同名方法。默认返回super.同名方法。

super.同名方法的返回情况其实就是上面试过的。
1、在parent的dispatchTouchEvent不调用super.dispatchTouchEvent依次返回true和false：
true，点击child1：
I/ondispatch: activity dispatchTouchEvent—->
I/ondispatch: parent dispatchTouchEvent—->parent
I/ondispatch: activity dispatchTouchEvent—->
I/ondispatch: parent dispatchTouchEvent—->parent
I/ondispatch: activity dispatchTouchEvent—->
I/ondispatch: parent dispatchTouchEvent—->parent

I/dispatched: activity dispatchTouchEvent—->action_down——>
I/dispatched: parent dispatchTouchEvent—->action_down——>parent
I/dispatched: activity dispatchTouchEvent—->action_move——>
I/dispatched: parent dispatchTouchEvent—->action_move——>parent
I/dispatched: activity dispatchTouchEvent—->action_up——>
I/dispatched: parent dispatchTouchEvent—->action_up——>parent

可以看到down、move、up都在parent的dispatchTouchEvent处理完了。没有再往下走。
false，点击child1：

I/ondispatch: activity dispatchTouchEvent—->
I/ondispatch: parent dispatchTouchEvent—->parent
I/ondispatch: activity onTouchEvent—->
I/ondispatch: activity dispatchTouchEvent—->
I/ondispatch: activity onTouchEvent—->
I/ondispatch: activity dispatchTouchEvent—->
I/ondispatch: activity onTouchEvent—->

I/dispatched: activity dispatchTouchEvent—->action_down——>
I/dispatched: parent dispatchTouchEvent—->action_down——>parent
I/dispatched: activity onTouchEvent—->action_down——>
I/dispatched: activity dispatchTouchEvent—->action_move——>
I/dispatched: activity onTouchEvent—->action_move——>
I/dispatched: activity dispatchTouchEvent—->action_up——>
I/dispatched: activity onTouchEvent—->action_up——>
这个有点惨，parent dispatchTouchEvent只有down事件。后面由activity的onTouchEvent接受down事件，然后move和up走activity的分发：
activity dispatchTouchEvent－－》onTouchEvent

调用super.dispatchTouchEvent看看吧～
返回true，点击child1：

I/dispatched: activity dispatchTouchEvent—->action_down——>
I/dispatched: parent dispatchTouchEvent—->action_down——>parent
I/dispatched: parent onInterceptTouchEvent—->action_down——>parent
I/dispatched: parentTwo dispatchTouchEvent—->action_down——>parentTwo
I/dispatched: parentTwo onInterceptTouchEvent—->action_down——>parentTwo
I/dispatched: child dispatchTouchEvent—->action_down——>child1
I/dispatched: child onTouchEvent—->action_down——>child1
I/dispatched: activity dispatchTouchEvent—->action_up——>
I/dispatched: parent dispatchTouchEvent—->action_up——>parent
I/dispatched: parent onInterceptTouchEvent—->action_up——>parent
I/dispatched: parentTwo dispatchTouchEvent—->action_up——>parentTwo
I/dispatched: parentTwo onInterceptTouchEvent—->action_up——>parentTwo
I/dispatched: child dispatchTouchEvent—->action_up——>child1
I/dispatched: child onTouchEvent—->action_up——>child1
事件走向：
activity dispatchTouchEvent －－》parent dispatchTouchEvent、onInterceptTouchEvent－－》parentTwo dispatchTouchEvent、onInterceptTouchEvent－－》child dispatchTouchEvent、onTouchEvent。这个和返回super是一样的。

返回false：

I/dispatched: activity dispatchTouchEvent—->action_down——>
I/dispatched: parent dispatchTouchEvent—->action_down——>parent
I/dispatched: parent onInterceptTouchEvent—->action_down——>parent
I/dispatched: parentTwo dispatchTouchEvent—->action_down——>parentTwo
I/dispatched: parentTwo onInterceptTouchEvent—->action_down——>parentTwo
I/dispatched: child dispatchTouchEvent—->action_down——>child1
I/dispatched: child onTouchEvent—->action_down——>child1
I/dispatched: activity onTouchEvent—->action_down——>
I/dispatched: activity dispatchTouchEvent—->action_up——>
I/dispatched: activity onTouchEvent—->action_up——>

down事件一直传递到最底层child1，然后没人处理，又传给了activity的onTouchEvent，然后后续的事件走向：activity dispatchTouchEvent －》onTouchEvent。最后交由了activity处理。

2、在parent 的onInterceptTouchEvent 里，super点击去是默认返回false，所以返回super和false是和开始什么都没处理是一样的。
重点是返回true，那么问题来了 在down、move、up中返回true是一样的吗？打个日志看看：
在down中返回true，点击child1：

I/dispatched: activity dispatchTouchEvent—->action_down——>
I/dispatched: parent dispatchTouchEvent—->action_down——>parent
I/dispatched: parent onInterceptTouchEvent—->action_down——>parent
I/dispatched: parent onTouchEvent—->action_down——>parent
I/dispatched: activity onTouchEvent—->action_down——>
I/dispatched: activity dispatchTouchEvent—->action_move——>
I/dispatched: activity onTouchEvent—->action_move——>
I/dispatched: activity dispatchTouchEvent—->action_move——>
I/dispatched: activity onTouchEvent—->action_move——>
I/dispatched: activity dispatchTouchEvent—->action_move——>
I/dispatched: activity onTouchEvent—->action_move——>
I/dispatched: activity dispatchTouchEvent—->action_up——>
I/dispatched: activity onTouchEvent—->action_up——>
可以看到 在parent一层中down事件dispatchTouchEvent——》onInterceptTouchEvent－－》onTouchEvent并没有往下一层parentTwo分发。然后down事件回到activity的onTouchEvent，后面事件就是由activity的dispatchTouchEvent－》onTouchEvent的正常流程。简单的说，parent的onInterceptTouchEvent 在down事件返回了true，会直接转到自己的onTouchEvent，但是后续事件自己接受不到，只能交给上一级的activity处理。

在move中返回true，点击child1；
I/dispatched: activity dispatchTouchEvent—->action_down——>
I/dispatched: parent dispatchTouchEvent—->action_down——>parent
I/dispatched: parent onInterceptTouchEvent—->action_down——>parent
I/dispatched: parentTwo dispatchTouchEvent—->action_down——>parentTwo
I/dispatched: parentTwo onInterceptTouchEvent—->action_down——>parentTwo
I/dispatched: child dispatchTouchEvent—->action_down——>child1
I/dispatched: child onTouchEvent—->action_down——>child1
I/dispatched: activity dispatchTouchEvent—->action_move——>
I/dispatched: parent dispatchTouchEvent—->action_move——>parent
I/dispatched: parent onInterceptTouchEvent—->action_move——>parent
I/dispatched: activity dispatchTouchEvent—->action_move——>
I/dispatched: parent dispatchTouchEvent—->action_move——>parent
I/dispatched: parent onTouchEvent—->action_move——>parent
I/dispatched: activity onTouchEvent—->action_move——>
I/dispatched: activity dispatchTouchEvent—->action_move——>
I/dispatched: parent dispatchTouchEvent—->action_move——>parent
I/dispatched: parent onTouchEvent—->action_move——>parent
I/dispatched: activity onTouchEvent—->action_move——>
I/dispatched: activity dispatchTouchEvent—->action_move——>
I/dispatched: parent dispatchTouchEvent—->action_move——>parent
I/dispatched: parent onTouchEvent—->action_move——>parent
I/dispatched: activity onTouchEvent—->action_move——>
I/dispatched: activity dispatchTouchEvent—->action_move——>
I/dispatched: parent dispatchTouchEvent—->action_move——>parent
I/dispatched: parent onTouchEvent—->action_move——>parent
I/dispatched: activity onTouchEvent—->action_move——>
I/dispatched: activity dispatchTouchEvent—->action_up——>
I/dispatched: parent dispatchTouchEvent—->action_up——>parent
I/dispatched: parent onTouchEvent—->action_up——>parent
I/dispatched: activity onTouchEvent—->action_up——>
down事件是正常传递的，然后move事件在onInterceptTouchEvent的时候被拦截，注意这里和down事件不一样：
down事件的过程是parent dispatchTouchEvent——》onInterceptTouchEvent－－》onTouchEvent，move事件没有直接到onTouchEvent，而是转到了activity的dispatchTouchEvent，再parent 的dispatchTouchEvent，接着这时候不再走parent的onInterceptTouchEvent，而是直接到了parent的onTouchEvent，再走activity的onTouchEvent，up事件也是一样。
单把parent的捞出来看

I/dispatched: parent dispatchTouchEvent—->action_down——>parent
I/dispatched: parent onInterceptTouchEvent—->action_down——>parent
I/dispatched: parent dispatchTouchEvent—->action_move——>parent
I/dispatched: parent onInterceptTouchEvent—->action_move——>parent
I/dispatched: parent dispatchTouchEvent—->action_move——>parent
I/dispatched: parent onTouchEvent—->action_move——>parent
I/dispatched: parent dispatchTouchEvent—->action_up——>parent
I/dispatched: parent onTouchEvent—->action_up——>parent

可以看到，move和up事件都传递到了parent的onTouchEvent，但是down事件没有，down事件最后一站在child1的onTouchEvent。而且onInterceptTouchEvent在返回了true之后不再出现。

在up事件中返回true，点击child1：
I/dispatched: activity dispatchTouchEvent—->action_down——>
I/dispatched: parent dispatchTouchEvent—->action_down——>parent
I/dispatched: parent onInterceptTouchEvent—->action_down——>parent
I/dispatched: parentTwo dispatchTouchEvent—->action_down——>parentTwo
I/dispatched: parentTwo onInterceptTouchEvent—->action_down——>parentTwo
I/dispatched: child dispatchTouchEvent—->action_down——>child1
I/dispatched: child onTouchEvent—->action_down——>child1
I/dispatched: activity dispatchTouchEvent—->action_move——>
I/dispatched: parent dispatchTouchEvent—->action_move——>parent
I/dispatched: parent onInterceptTouchEvent—->action_move——>parent
I/dispatched: parentTwo dispatchTouchEvent—->action_move——>parentTwo
I/dispatched: parentTwo onInterceptTouchEvent—->action_move——>parentTwo
I/dispatched: child dispatchTouchEvent—->action_move——>child1
I/dispatched: child onTouchEvent—->action_move——>child1
I/dispatched: activity dispatchTouchEvent—->action_move——>
I/dispatched: parent dispatchTouchEvent—->action_move——>parent
I/dispatched: parent onInterceptTouchEvent—->action_move——>parent
I/dispatched: parentTwo dispatchTouchEvent—->action_move——>parentTwo
I/dispatched: parentTwo onInterceptTouchEvent—->action_move——>parentTwo
I/dispatched: child dispatchTouchEvent—->action_move——>child1
I/dispatched: child onTouchEvent—->action_move——>child1
I/dispatched: activity dispatchTouchEvent—->action_up——>
I/dispatched: parent dispatchTouchEvent—->action_up——>parent
I/dispatched: parent onInterceptTouchEvent—->action_up——>parent

和move有些类似：down、move事件正常传递到child1的onTouchEvent就停止了。然后由activity
dispatchTouchEvent－－》parent dispatchTouchEvent、onInterceptTouchEvent。parent onTouchEvent没有接受up事件，activity onTouchEvent也没有。

3、在parent 的onTouchEvent的中不调用super直接返回true、false,点击child1：
返回true：
I/dispatched: activity dispatchTouchEvent—->action_down——>
I/dispatched: parent dispatchTouchEvent—->action_down——>parent
I/dispatched: parent onInterceptTouchEvent—->action_down——>parent
I/dispatched: parentTwo dispatchTouchEvent—->action_down——>parentTwo
I/dispatched: parentTwo onInterceptTouchEvent—->action_down——>parentTwo
I/dispatched: child dispatchTouchEvent—->action_down——>child1
I/dispatched: child onTouchEvent—->action_down——>child1
I/dispatched: activity dispatchTouchEvent—->action_move——>
I/dispatched: parent dispatchTouchEvent—->action_move——>parent
I/dispatched: parent onInterceptTouchEvent—->action_move——>parent
I/dispatched: parentTwo dispatchTouchEvent—->action_move——>parentTwo
I/dispatched: parentTwo onInterceptTouchEvent—->action_move——>parentTwo
I/dispatched: child dispatchTouchEvent—->action_move——>child1
I/dispatched: child onTouchEvent—->action_move——>child1
I/dispatched: activity dispatchTouchEvent—->action_move——>
I/dispatched: parent dispatchTouchEvent—->action_move——>parent
I/dispatched: parent onInterceptTouchEvent—->action_move——>parent
I/dispatched: parentTwo dispatchTouchEvent—->action_move——>parentTwo
I/dispatched: parentTwo onInterceptTouchEvent—->action_move——>parentTwo
I/dispatched: child dispatchTouchEvent—->action_move——>child1
I/dispatched: child onTouchEvent—->action_move——>child1
I/dispatched: activity dispatchTouchEvent—->action_move——>
I/dispatched: parent dispatchTouchEvent—->action_move——>parent
I/dispatched: parent onInterceptTouchEvent—->action_move——>parent
I/dispatched: parentTwo dispatchTouchEvent—->action_move——>parentTwo
I/dispatched: parentTwo onInterceptTouchEvent—->action_move——>parentTwo
I/dispatched: child dispatchTouchEvent—->action_move——>child1
I/dispatched: child onTouchEvent—->action_move——>child1
I/dispatched: activity dispatchTouchEvent—->action_up——>
I/dispatched: parent dispatchTouchEvent—->action_up——>parent
I/dispatched: parent onInterceptTouchEvent—->action_up——>parent
I/dispatched: parentTwo dispatchTouchEvent—->action_up——>parentTwo
I/dispatched: parentTwo onInterceptTouchEvent—->action_up——>parentTwo
I/dispatched: child dispatchTouchEvent—->action_up——>child1
I/dispatched: child onTouchEvent—->action_up——>child1

move的部分有些重复，但是没关系，还是能看出来，是正常的传递。

返回false：
I/dispatched: activity dispatchTouchEvent—->action_down——>
I/dispatched: parent dispatchTouchEvent—->action_down——>parent
I/dispatched: parent onInterceptTouchEvent—->action_down——>parent
I/dispatched: parentTwo dispatchTouchEvent—->action_down——>parentTwo
I/dispatched: parentTwo onInterceptTouchEvent—->action_down——>parentTwo
I/dispatched: child dispatchTouchEvent—->action_down——>child1
I/dispatched: child onTouchEvent—->action_down——>child1
I/dispatched: activity dispatchTouchEvent—->action_move——>
I/dispatched: parent dispatchTouchEvent—->action_move——>parent
I/dispatched: parent onInterceptTouchEvent—->action_move——>parent
I/dispatched: parentTwo dispatchTouchEvent—->action_move——>parentTwo
I/dispatched: parentTwo onInterceptTouchEvent—->action_move——>parentTwo
I/dispatched: child dispatchTouchEvent—->action_move——>child1
I/dispatched: child onTouchEvent—->action_move——>child1
I/dispatched: activity dispatchTouchEvent—->action_move——>
I/dispatched: parent dispatchTouchEvent—->action_move——>parent
I/dispatched: parent onInterceptTouchEvent—->action_move——>parent
I/dispatched: parentTwo dispatchTouchEvent—->action_move——>parentTwo
I/dispatched: parentTwo onInterceptTouchEvent—->action_move——>parentTwo
I/dispatched: child dispatchTouchEvent—->action_move——>child1
I/dispatched: child onTouchEvent—->action_move——>child1
I/dispatched: activity dispatchTouchEvent—->action_move——>
I/dispatched: parent dispatchTouchEvent—->action_move——>parent
I/dispatched: parent onInterceptTouchEvent—->action_move——>parent
I/dispatched: parentTwo dispatchTouchEvent—->action_move——>parentTwo
I/dispatched: parentTwo onInterceptTouchEvent—->action_move——>parentTwo
I/dispatched: child dispatchTouchEvent—->action_move——>child1
I/dispatched: child onTouchEvent—->action_move——>child1
I/dispatched: activity dispatchTouchEvent—->action_up——>
I/dispatched: parent dispatchTouchEvent—->action_up——>parent
I/dispatched: parent onInterceptTouchEvent—->action_up——>parent
I/dispatched: parentTwo dispatchTouchEvent—->action_up——>parentTwo
I/dispatched: parentTwo onInterceptTouchEvent—->action_up——>parentTwo
I/dispatched: child dispatchTouchEvent—->action_up——>child1
I/dispatched: child onTouchEvent—->action_up——>child1
发现一样。
原因是点击child1，上面那张图的左半边是没有影响的，到child1的onTouchEvent就由child1接受了根本不会跑到parentTwo、parent的onTouchEvent。所以在parent的onTouchEvent中返回是没用的。

点击parent自己，返回true：
I/dispatched: activity dispatchTouchEvent—->action_down——>
I/dispatched: parent dispatchTouchEvent—->action_down——>parent
I/dispatched: parent onInterceptTouchEvent—->action_down——>parent
I/dispatched: parent onTouchEvent—->action_down——>parent
I/dispatched: activity dispatchTouchEvent—->action_move——>
I/dispatched: parent dispatchTouchEvent—->action_move——>parent
I/dispatched: parent onTouchEvent—->action_move——>parent
I/dispatched: activity dispatchTouchEvent—->action_up——>
I/dispatched: parent dispatchTouchEvent—->action_up——>parent
I/dispatched: parent onTouchEvent—->action_up——>parent
点击parent自己，返回false：

I/dispatched: activity dispatchTouchEvent—->action_down——>
I/dispatched: parent dispatchTouchEvent—->action_down——>parent
I/dispatched: parent onInterceptTouchEvent—->action_down——>parent
I/dispatched: parent onTouchEvent—->action_down——>parent
I/dispatched: activity onTouchEvent—->action_down——>
I/dispatched: activity dispatchTouchEvent—->action_move——>
I/dispatched: activity onTouchEvent—->action_move——>
I/dispatched: activity dispatchTouchEvent—->action_up——>
I/dispatched: activity onTouchEvent—->action_up——>
可以看到parent onTouchEvent只接受到down事件。然后交由activity处理。

三、总结
1、事件传递的方向是由activity－－》父视图－－》子视图
2、触摸动作最终由哪个视图处理，哪个视图onTouchEvent方法接受move和up。
3、dispatchTouchEvent返回true，down、move、up都在dispatchTouchEvent中处理不会继续下发；返回false，会由上一级视图的onTouchEvent处理。
4、onInterceptTouchEvent返回true，事件会转到当前视图的onTouchEvent，但是如果拦截了down事件，onTouchEvent不会收到其他事件；拦截了move事件，down事件正常走到子视图的onTouchEvent，当前视图的onTouchEvent接受不到。
5、视图默认不处理手指动作的，除非设置了setClickable、setLongClickable、或者添加了点击或者触摸监听（本质就是setClickable、setLongClickable）。

阿呆不高
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
30分钟搞清楚Android Touch事件分发机制
09-02
30分钟搞清楚Android Touch事件分发机制,Touch事件分发中只有两个主角:ViewGroup和View，想要深入学习的朋友可以参考本
Android体系架构之事件分发机制探究
博主逸尘
04-03 173
事件分发是作为一名Android开发者必须要掌握的东西，下面我们来一起探究下是如何进行事件分发的 首先我们要搞明白，什么是事件分发？Android中的视图是由一个个View嵌套构成的层级视图，即一个View里包含有子View，而这个子View里面又可以再添加View。当用户触摸屏幕产生一系列事件时，事件会由高到低，由外向内依次传递，最终把事件交到一个具体的View手上处理，这个传递...
深入源码理解Android Touch事件分发机制（上篇）
itheimaleevi的博客
09-03 1226
首先，说到Touch事件分发机制，那我们就要弄清楚什么事Touch事件？我们通常说的Touch事件，它其实并不简简单单是一个事件，它是由1个DOWN事件，n个MOVE事件，1个UP事件构成的，当然在这里n可以为零。也就是说，一个完整的Touch事件，必须有且只有1个DOWN事件和1个UP事件，中间还可以穿插若干个MOVE 事件。 那接下来就来弄清楚我们经常听到的onTouch、onTouchEvent、onClick，这三者之间又有什么区别和联系呢？要弄清楚这个问题我们还是要借助源码和一个非常简
一步步探索学习Android Touch事件分发传递机制（一）
小莫(Alan_Mo)的博客
11-13 396
Android TouchEvent 简介1.探究对象简介 Android的屏幕触摸事件在Android官方API中由类MotionEvent来描述，不同的触摸事件对应不同的事件类型。 如：ACTION_DOWN;ACTION_UP;ACTION_MOVE;ACTION_CANCEL 每个事件对应都有自己的传递路径，从产生到传递到最终被消费（终止传递）。而它们的传递的载体就是整颗View树。 毕竟
深入透析Android事件分发机制
TaoLee
11-07 1828
一、 Android分发机制概述： Android如此受欢迎，就在于其优秀的交互性，这其中，Android优秀的事件分发机制功不可没。那么，作为一个优秀的程序员，要想做一个具有良好交互性的应用，必须透彻理解Android的事件分发机制。 要想充分理解android的分发机制，需要先对以下几个知识点有所了解： ① View和ViewGroup什么？② 事件③ View 事件的
AndroidTouch事件传递机制解析
01-31
touch机制好好看了一下，呵呵。。android系统中的每个ViewGroup的子类都具有下面三个和TouchEvent处理密切相关的方法：1）publicbooleandispatchTouchEvent(MotionEvent ev)这个方法用来分发TouchEvent2）...
Android Touch事件分发机制代码一
05-19
详细了解可以查看链接：http://blog.csdn.net/hnulwt/article/details/45847737非常简单的测试小demo，有关于android事件分发机制的。
Android Touch事件分发过程详解
09-04
主要介绍了Android Touch事件分发过程,详细描述了Android Touch事件的主要处理流程,有助于深入理解Android程序设计,需要的朋友可以参考下
记一次webview 中使用shouldInterceptRequest的踩坑
热门推荐
y1962475006的博客
12-08 2万+
shouldInterceptRequest 是WebViewClient的一个方法，官方的说明： /** * Notify the host application of a resource request and allow the * application to return the data. If the return value is null, the We...
android 屏幕坐标总结
y1962475006的博客
03-14 1万+
android 屏幕坐标好多个，有时候傻傻分不清楚，经常记错，然后只能一个个试。尴尬～～ 把它们总结下来，以备不时之需嘿嘿。 一、视图坐标 最外面一层是屏幕，左上角是坐标原点，向右向下是x、y正方向。中间那层是父视图，里面是具体的某个子view。分为三组： getX：子view左边到父视图左边的距离； getY：子view上边到父视图上边的距离；getTop：子view上边到父视图上边
android 应用内悬浮框，并在指定页面显示
y1962475006的博客
06-06 9926
一、实现悬浮悬浮框基本的实现方式有两种： 1、 在一个页面内，可以用FrameLayout 或者RelativeLayout。FrameLayout 中view是在左上角堆叠的，也就是说是z-order的，所以可以页面的基布局是FrameLayout，然后在上面放一个view，并且更新view的translationX ，translationY来改变位置。 RelativeLayout 可以
IOC的两种简单实现
y1962475006的博客
07-30 8473
IOC的两种简单实现 上一次简单介绍过IOC的概念以及大体实现思路。IOC总结一句话就是框架帮开发者生成对象，以达到解耦的目的。牢牢记住这句话，如果把“如何帮开发者生成对象“作为题目，那么这次文章就是解这个题目的过程。 上次说到，IOC的两种实现思路： 1、反射； 2、new 对象。 比如现在有两个类，Computer 和 Host类。 Computer.java public cl...
popupwindow获取宽高
y1962475006的博客
01-31 5214
我们在确定popupwindow的时候会用到 showAtLocation(View parent, int gravity, int x, int y) api，这个api的入參： @param parent a parent view to get the {@link android.view.View#getWindowToken()} token from * @param gra
ARouter使用和案例
y1962475006的博客
10-12 4391
ARouter的使用 官网github： https://github.com/alibaba/ARouter/blob/master/README_CN.md 这里对其做了分类整理，便于更方便理解。 跳转 跳转Activity 1、path跳转 path的规则：/group/child…至少两个“/”；和Activity的@Route注解值匹配 // 构建标准的路由请求 ARouter.getI...
从android HashMap的源码实现谈谈HashMap的性能问题
y1962475006的博客
12-19 3600
从android HashMap的源码实现谈谈HashMap的性能问题前言实际开发中，HashMap可能是我们用的最多的数据结构了。基础稍微扎实一点的开发，问起HashMap的特性，都会说，HashMap是key可以为null的，无序的，非线程安全的。没错，这几点确实是HashMap的特性，但是HashMap究竟为什么是非线程安全的，多线程下会有什么问题，作为“有理想”的程序员，都不应该放过。预备知
MVP中Presenter复用思路和Inject-mvp
y1962475006的博客
09-23 3207
MVP模式早已经不是什么新鲜词了，这里不再赘述。最近在重构代码的过程中，发现了一件及其痛苦的事情：很多时候，model层在应用中是很薄的，大多数的业务逻辑都在Presenter层，但是由于模版 代码，Activity（View）-&amp;amp;amp;amp;gt;P是一一对应绑定的关系，那这样，相当于只是把原来在Activity中的逻辑转移到了Presenter中，虽然一定程度上解耦了，方便单测了，但是事实上Present...
从两种单例模式谈java类加载过程中静态变量的初始化问题
y1962475006的博客
10-20 1914
前言 之前的文章里有总结过java的单例怎么写，具体链接 java中的7种单例模式。 经常听到，类的static变量在类加载时就会初始化，于是有了常说的两种单例模式的对比：饿汉式和静态内部类模式。通常的说法是，两种都是支持线程安全的（关于怎么个安全法请看我上面的链接），饿汉式不被推荐是因为会提前初始化，占用一部分内存。 那我们就用代码说话。 验证 根据jvm加载class文件的过程，先是讲clas...
IOC的概念以及简单实现的思路
y1962475006的博客
07-30 1466
IOC的概念以及简单实现的思路 what 控制反转（Inversion of Control，英文缩写为IoC）把创建对象的权利交给框架,是框架的重要特征，并非面向对象编程的专用术语。它包括依赖注入（Dependency Injection，简称DI）和依赖查找（Dependency Lookup） 以上是百度百科的内容，当然看起来官方的不得了。我们今天当然不会去扣这样的字眼。 ...
vue的touch事件
最新发布
12-26
需要注意的是，touch事件和click事件是两种不同的事件，它们的触发机制和优先级也不同。在移动端，当用户触摸屏幕时，会先触发touch事件，然后才会触发click事件。因此，在处理移动端事件时，需要注意touch事件的...

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值