Android进阶——Android事件分发机制之dispatchTouchEvent、onInterceptTouchEvent、onTouchEvent

前言

Android事件分发机制可以说是我们Android工程师面试题中的必考题,弄懂它的原理是我们避不开的任务,所以长痛不如短痛,花点时间干掉他,废话不多说,开车啦

Android事件分发机制的简介

Android事件分发机制的发生在View与View之间或者ViewGroup与View之间具有镶嵌的视图上,而且视图上必须为点击可用。当一个点击事件产生后,它的传递过程遵循如下顺序:Activity->Window->View,即事件先传递给Activity,再到Window,再到顶级View,才开始我们的事件分发

Android事件分发机制的相关概念

Android事件分发机制主要由三个重要的方法共同完成的

  • dispatchTouchEvent:用于进行点击事件的分发
  • onInterceptTouchEvent:用于进行点击事件的拦截
  • onTouchEvent:用于处理点击事件

这里需要注意的是View中是没有onInterceptTouchEvent()方法的

Android事件分发机制的分发例子

这里以两个ViewGroup嵌套View来演示,下面是演示图

[外链图片转存失败,源站可能有防盗链机制,建议将图片保存下来直接上传(img-v9FTiXLW-1661746720818)(https://img-blog.csdn.net/20170101234918740?watermark/2/text/aHR0cDovL2Jsb2cuY3Nkbi5uZXQvcXFfMzAzNzk2ODk=/font/5a6L5L2T/fontsize/400/fill/I0JBQkFCMA==/dissolve/70/gravity/SouthEast)]

一、MyView

继承View并覆写其三个构造方法,覆写dispatchTouchEvent和onTouchEvent

public class MyView extends View {
    public MyView(Context context) {
        super(context);
    }

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

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

    @Override
    public boolean dispatchTouchEvent(MotionEvent event) {
        System.out.println("MyView dispatchTouchEvent");
        return super.dispatchTouchEvent(event);
    }

    @Override
    public boolean onTouchEvent(MotionEvent event) {
        System.out.println("MyView onTouchEvent");
        return super.onTouchEvent(event);
    }
}

二、MyViewGroup01和MyViewGroup02

MyViewGroup01和MyViewGroup02是一样的代码,这里以01为例,继承ViewGroup并覆写其三个构造方法,覆写dispatchTouchEvent和onTouchEvent和onInterceptTouchEvent方法

public class MyViewGroup01 extends LinearLayout {

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

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

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

    @Override
    public boolean dispatchTouchEvent(MotionEvent ev) {
        System.out.println("MyViewGroup01 dispatchTouchEvent");
        return super.dispatchTouchEvent(ev);
    }

    @Override
    public boolean onInterceptTouchEvent(MotionEvent ev) {
        System.out.println("MyViewGroup01 onInterceptTouchEvent");
        return super.onInterceptTouchEvent(ev);
    }

    @Override
    public boolean onTouchEvent(MotionEvent event) {
        System.out.println("MyViewGroup01 onTouchEvent");
        return super.onTouchEvent(event);
    }
}

三、MyView和MyViewGroup布局文件

这里以ViewGroup和Group嵌套,由上面可以知道事件最后分配到布局的顶级View,这里的顶级View是MyViewGroup02,然后开始事件的传递

<?xml version="1.0" encoding="utf-8"?>
<com.handsome.boke2.TouchEvent.MyViewGroup02 xmlns:android="http://schemas.android.com/apk/res/android"
    android:layout_width="200dp"
    android:layout_height="200dp"
    android:background="#0f0">

    <com.handsome.boke2.TouchEvent.MyViewGroup01
        android:layout_width="100dp"
        android:layout_height="100dp"
        android:background="#f00">

        <com.handsome.boke2.TouchEvent.MyView
            android:layout_width="50dp"
            android:layout_height="50dp"
            android:background="#00f" />
    </com.handsome.boke2.TouchEvent.MyViewGroup01>
</com.handsome.boke2.TouchEvent.MyViewGroup02>

分析事件传递

点击MyView(即蓝色部分):先接收事件的是父容器(MyViewGroup02)往下分发,而事件的分发过程中分为两步骤

  • 分发过程
  • 处理过程

其正常的分发事件结果为

//分发过程
MyViewGroup02 dispatchTouchEvent
MyViewGroup02 onInterceptTouchEvent
MyViewGroup01 dispatchTouchEvent
MyViewGroup01 onInterceptTouchEvent
MyView dispatchTouchEvent
//处理过程
MyView onTouchEvent
MyViewGroup01 onTouchEvent
MyViewGroup02 onTouchEvent

1、dispatchTouchEvent(分发事件)

如果在MyViewGroup01的dispatchTouchEvent方法中返回true,表示需要在MyViewGroup01消费了整个事件,即不会再分发,也不会再处理。dispatchTouchEvent方法中返回true的打印信息

//分发过程
MyViewGroup02 dispatchTouchEvent
MyViewGroup02 onInterceptTouchEvent
MyViewGroup01 dispatchTouchEvent

如果在MyViewGroup01的dispatchTouchEvent方法中返回false,表示在MyViewGroup01点击事件在本层不再继续进行分发,并交由上层控件的onTouchEvent方法进行消费。dispatchTouchEvent方法中返回false的打印信息

//分发过程
MyViewGroup02 dispatchTouchEvent
MyViewGroup02 onInterceptTouchEvent
MyViewGroup01 dispatchTouchEvent
//处理过程
MyViewGroup02 onTouchEvent

2、onInterceptTouchEvent(拦截事件)

如果在MyViewGroup01的onInterceptTouchEvent方法中返回true,表示需要在MyViewGroup01拦截这个点击事件,不再继续往下分发,即MyView不再执行dispatchTouchEvent方法。但是只是分发结束了而已,接着开始处理事件。下面是onInterceptTouchEvent方法中返回true的打印信息

//分发过程
MyViewGroup02 dispatchTouchEvent
MyViewGroup02 onInterceptTouchEvent
MyViewGroup01 dispatchTouchEvent
MyViewGroup01 onInterceptTouchEvent
//处理过程
MyViewGroup01 onTouchEvent
MyViewGroup02 onTouchEvent

如果在MyViewGroup01的onInterceptTouchEvent方法中返回false,表示需要在MyViewGroup01不会拦截这个点击事件,继续往下分发。下面是onInterceptTouchEvent方法中返回false的打印信息

//分发过程
MyViewGroup02 dispatchTouchEvent
MyViewGroup02 onInterceptTouchEvent
MyViewGroup01 dispatchTouchEvent
MyViewGroup01 onInterceptTouchEvent
MyView dispatchTouchEvent
//处理过程
MyView onTouchEvent
MyViewGroup01 onTouchEvent
MyViewGroup02 onTouchEvent

3、onTouchEvent(消费事件)

如果MyViewGroup01的onTouchEvent方法中返回true,表示MyViewGroup01可以将该事件直接消费掉了,即分发结束后,处理事件的时候,直接处理到MyViewGroup01就可以结束了。下面是onTouchEvent方法中返回true的打印信息

//分发过程
MyViewGroup02 dispatchTouchEvent
MyViewGroup02 onInterceptTouchEvent
MyViewGroup01 dispatchTouchEvent
MyViewGroup01 onInterceptTouchEvent
MyView dispatchTouchEvent
//处理过程
MyView onTouchEvent
MyViewGroup01 onTouchEvent

如果MyViewGroup01的onTouchEvent方法中返回false,表示MyViewGroup01不可以将该事件直接消费掉,即事件继续往上处理。下面是onTouchEvent方法中返回false的打印信息

//分发过程
MyViewGroup02 dispatchTouchEvent
MyViewGroup02 onInterceptTouchEvent
MyViewGroup01 dispatchTouchEvent
MyViewGroup01 onInterceptTouchEvent
MyView dispatchTouchEvent
//处理过程
MyView onTouchEvent
MyViewGroup01 onTouchEvent
MyViewGroup02 onTouchEvent

总结起来:

  • dispatchTouchEvent
    • return true:表示该View内部消化掉了所有事件
    • return false:表示事件在本层不再继续进行分发,并交由上层控件的onTouchEvent方法进行消费
    • return super.dispatchTouchEvent(ev):默认事件将分发给本层的事件拦截onInterceptTouchEvent方法进行处理
  • onInterceptTouchEvent
    • return true:表示将事件进行拦截,并将拦截到的事件交由本层控件的onTouchEvent进行处理
    • return false:表示不对事件进行拦截,事件得以成功分发到子View
    • return super.onInterceptTouchEvent(ev):默认表示不拦截该事件,并将事件传递给下一层View的dispatchTouchEvent
  • onTouchEvent
    • return true:表示onTouchEvent处理完事件后消费了此次事件
    • return fasle:表示不响应事件,那么该事件将会不断向上层View的onTouchEvent方法传递,直到某个View的onTouchEvent方法返回true
    • return super.dispatchTouchEvent(ev):表示不响应事件,结果与return false一样

Android事件分发机制的分发流程

这里以网上的图片来说明,如果对上面分发例子还不太懂的同学,看这张图片已经很生动的说明了整个过程

[外链图片转存失败,源站可能有防盗链机制,建议将图片保存下来直接上传(img-IIIvOhxZ-1661746720819)(https://img-blog.csdn.net/20170101220052950?watermark/2/text/aHR0cDovL2Jsb2cuY3Nkbi5uZXQvcXFfMzAzNzk2ODk=/font/5a6L5L2T/fontsize/400/fill/I0JBQkFCMA==/dissolve/70/gravity/SouthEast)]

ViewGroup事件分发源码分析

我们这里以ViewGroup的dispatchTouchEvent()方法开始讲解,这里面主要有两件事情

  • 询问是否拦截事件
  • 遍历子View并分发事件

一、dispatchTouchEvent源码询问拦截事件

@Override
public boolean dispatchTouchEvent(MotionEvent ev) {
		
	......
	
	// Check for interception.
	final boolean intercepted;
	//这里检查是否拦截事件
	if (actionMasked == MotionEvent.ACTION_DOWN
	        || mFirstTouchTarget != null) {
	    final boolean disallowIntercept = (mGroupFlags & FLAG_DISALLOW_INTERCEPT) != 0;
	    if (!disallowIntercept) {
	        intercepted = onInterceptTouchEvent(ev);
	        ev.setAction(action); // restore action in case it was changed
	    } else {
	        intercepted = false;
	    }
	} else {
	    // There are no touch targets and this action is not an initial down
	    // so this view group continues to intercept touches.
	    intercepted = true;
	}

	......
}

ViewGroup在两种情况下都会判断是否要拦截当前事件

  • 事件类型为ACTION_DOWN:当前由我们触发的点击事件,也即是说ACTION_MOVE和ACTION_UP事件来时,则不触发拦截事件
  • mFirstTouchTarget != null:当ViewGroup不拦截事件并将事件交给子View的时候该不等式成立。反过来,事件被ViewGroup拦截时,该不等式不成立

二、dispatchTouchEvent源码遍历子View并分发事件

@Override
public boolean dispatchTouchEvent(MotionEvent ev) {
		
	......
	
	final View[] children = mChildren;
	//遍历所有子View
	for (int i = childrenCount - 1; i >= 0; i--) {
	    final int childIndex = getAndVerifyPreorderedIndex(
	            childrenCount, i, customOrder);
	    final View child = getAndVerifyPreorderedView(
	            preorderedList, children, childIndex);
	
	    //判断子View是否能接收点击事件
	    if (childWithAccessibilityFocus != null) {
	        if (childWithAccessibilityFocus != child) {
	            continue;
	        }
	        childWithAccessibilityFocus = null;
	        i = childrenCount - 1;
	    }
	
		//判断子元素在播放动画时落在子元素的区域内
	    if (!canViewReceivePointerEvents(child)
	            || !isTransformedTouchPointInView(x, y, child, null)) {
	        ev.setTargetAccessibilityFocus(false);
	        continue;
	    }
	    
		//判断子元素点击事件是否落在子元素的区域内
	    newTouchTarget = getTouchTarget(child);
	    if (newTouchTarget != null) {
	        // Child is already receiving touch within its bounds.
	        // Give it the new pointer in addition to the ones it is handling.
	        newTouchTarget.pointerIdBits |= idBitsToAssign;
	        break;
	    }
	
	    resetCancelNextUpFlag(child);
	    //事件传递到子View,下面追踪该方法
	    if (dispatchTransformedTouchEvent(ev, false, child, idBitsToAssign)) {
	        // Child wants to receive touch within its bounds.
	        mLastTouchDownTime = ev.getDownTime();
	        if (preorderedList != null) {
	            // childIndex points into presorted list, find original index
	            for (int j = 0; j < childrenCount; j++) {
	                if (children[childIndex] == mChildren[j]) {
	                    mLastTouchDownIndex = j;
	                    break;
	                }
	            }
	        } else {
	            mLastTouchDownIndex = childIndex;
	        }
	        mLastTouchDownX = ev.getX();
	        mLastTouchDownY = ev.getY();
	        newTouchTarget = addTouchTarget(child, idBitsToAssign);
	        alreadyDispatchedToNewTouchTarget = true;
	        break;
	    }
	
	    // The accessibility focus didn't handle the event, so clear
	    // the flag and do a normal dispatch to all children.
	    ev.setTargetAccessibilityFocus(false);
	}

	......
}

ViewGroup直接使用for遍历所有子View,对子View的各种状态进行判断,最后调用dispatchTransformedTouchEvent(ev, false, child, idBitsToAssign)将事件传递给子View,下面是dispatchTransformedTouchEvent()方法的部分源码

if (child == null) {
    handled = super.dispatchTouchEvent(event);
} else {
    handled = child.dispatchTouchEvent(event);
}

其最后就是分发给子View的dispatchTouchEvent()方法,那么事件就分发到子View中去了

View事件分发源码分析

View对点击事件的处理过程主要有

  • View的dispatchTouchEvent():判断分发事件
  • View的onTouchEvent():处理事件的具体做法

一、dispatchTouchEvent源码判断分发事件部分

public boolean dispatchTouchEvent(MotionEvent event) {

	boolean result = false;
	......
	if (onFilterTouchEventForSecurity(event)) {
	    if ((mViewFlags & ENABLED_MASK) == ENABLED && handleScrollBarDragging(event)) {
	        result = true;
	    }
	    //noinspection SimplifiableIfStatement
	    ListenerInfo li = mListenerInfo;
	    //这里开始判断
	    if (li != null && li.mOnTouchListener != null
	            && (mViewFlags & ENABLED_MASK) == ENABLED
	            && li.mOnTouchListener.onTouch(this, event)) {
	        result = true;
	    }
	
	    if (!result && onTouchEvent(event)) {
	        result = true;
	    }
	}
	
	......
	return result;
}

从源码判断处看出,首先会判断有没有设置mOnTouchListener,如果mOnTouchListener不为空,那么onTouchEvent就不会被调用,这里可以得到一个结论,若在View中设置了OnTouchListener,那么它的优先级是高于onTouchEvent的,这样可以更好的让我们自己setOnTouchEventListener()处理点击事件

二、onTouchEvent源码处理事件的具体做法部分

public boolean onTouchEvent(MotionEvent event) {
	......
	//当View处于不可用状态下,也会消耗点击事件
	if ((viewFlags & ENABLED_MASK) == DISABLED) {
        if (action == MotionEvent.ACTION_UP && (mPrivateFlags & PFLAG_PRESSED) != 0) {
            setPressed(false);
        }
        // A disabled view that is clickable still consumes the touch
        // events, it just doesn't respond to them.
        return (((viewFlags & CLICKABLE) == CLICKABLE
                || (viewFlags & LONG_CLICKABLE) == LONG_CLICKABLE)
                || (viewFlags & CONTEXT_CLICKABLE) == CONTEXT_CLICKABLE);
    }

	......
	//对点击事件的具体处理
	if (((viewFlags & CLICKABLE) == CLICKABLE ||
            (viewFlags & LONG_CLICKABLE) == LONG_CLICKABLE) ||
            (viewFlags & CONTEXT_CLICKABLE) == CONTEXT_CLICKABLE) {
        switch (action) {
            case MotionEvent.ACTION_UP:
                boolean prepressed = (mPrivateFlags & PFLAG_PREPRESSED) != 0;
                if ((mPrivateFlags & PFLAG_PRESSED) != 0 || prepressed) {
                    ......
                    if (!mHasPerformedLongPress && !mIgnoreNextUpEvent) {
                        // This is a tap, so remove the longpress check
                        removeLongPressCallback();

                        // Only perform take click actions if we were in the pressed state
                        if (!focusTaken) {
                            // Use a Runnable and post this rather than calling
                            // performClick directly. This lets other visual state
                            // of the view update before click actions start.
                            if (mPerformClick == null) {
                                mPerformClick = new PerformClick();
                            }
                            if (!post(mPerformClick)) {
                                performClick();
                            }
                        }
                    }
					......
				}
        }

        return true;
    }
    ......
}

从对点击事件的具体处理中看出,只要View的CLICKABLE和LONG_CLICKABLE有一个为true,那么它就会消耗这个事件,即onTouchEvent方法返回true。在ACTION_UP事件中,会触发PerformClick()方法,如果View设置了OnClickListener,那么PerformClick()方法内部会调用它的onClick()方法,这里就不分析它的点击事件了

View事件方法执行顺序

onTouchListener > onTouchEvent > onLongClickListener > onClickListener

面试题

1、简要的谈谈Android的事件分发机制?

当点击事件发生时,首先Activity将TouchEvent传递给Window,再从Window传递给顶层View。TouchEvent会最先到达最顶层 view 的 dispatchTouchEvent ,然后由 dispatchTouchEvent 方法进行分发,如果dispatchTouchEvent返回true ,则整个事件将会被销毁,如果dispatchTouchEvent返回 false ,则交给上层view的 onTouchEvent 方法来开始处理这个事件,如果 interceptTouchEvent 返回 true ,也就是拦截掉了,则交给自身的 onTouchEvent 来处理,如果 interceptTouchEvent 返回 false ,那么事件将继续传递给子 view ,由子 view 的 dispatchTouchEvent 再来开始这个事件的分发。如果事件传递到某一层的子 view 的 onTouchEvent 上了,且这个方法返回了 false ,那么这个事件会从这个 view 往上传递,都是 onTouchEvent 来接收,直到onTouchEvent返回true为止。而如果传递到最顶view的 onTouchEvent 也返回 false 的话,这个事件就会消失。

2、为什么View有dispatchTouchEvent方法?

因为View可以注册很多事件的监听器,如长按、滑动、点击等,它也需要一个管理者来分发

3、ViewGroup中可能有很多个子View,如何判断应该分配给哪一个?

根据源码可知,它会分配给在点击范围内的子View

4、当点击时,子View重叠应该如何分配?

一般分配给最上层的子View,这是由于安卓的渲染机制导致的

结语

事件分发机制就犹如数学的定理是一样道理的,只有记住定理,才能在具体应用中具体分析,有人可能不知道在什么地方会用到,如果你做的项目中,比如有一个控件点击不能反应,那么就有可能是事件分发的结果。至于对源码的分析可能内容比较复杂,内容也多,源码部分有些也让我不是很懂,这里是浅析一下,做个开头,希望大家下去有时间可以翻源码去理解这一机制,将它运用在实战中吧


前语

接上次的更新,这次更新两个例子,嵌套View和同级View的事件传递过程。上面所说的只是适用于嵌套类型的事件冲突,但如果是同级关系的话,又是另一种表现

温习多个View嵌套

通过颜色一层层的嵌套,模拟事件分发

<RelativeLayout xmlns:android="http://schemas.android.com/apk/res/android"
    android:layout_width="match_parent"
    android:layout_height="match_parent"">

    <com.hensen.touch.Yellow
        android:id="@+id/yellow"
        android:layout_width="match_parent"
        android:layout_height="match_parent"
        android:background="#ff0">

        <com.hensen.touch.Red
            android:id="@+id/red"
            android:layout_width="match_parent"
            android:layout_height="match_parent"
            android:layout_margin="80dp"
            android:background="#f00">

            <com.hensen.touch.Blue
                android:id="@+id/blue"
                android:layout_width="match_parent"
                android:layout_height="match_parent"
                android:layout_margin="80dp"
                android:background="#00f">

            </com.hensen.touch.Blue>
        </com.hensen.touch.Red>
    </com.hensen.touch.Yellow>
</RelativeLayout>
分发流程
  • dispatchTouchEvent:是否愿意分发事件
  • onInterceptTouchEvent:是否需要拦截事件
  • onTouchEvent:是否需要消费事件
分发步骤
  • 从关系角度来说,点击事件从父容器往子容器分发,再从子容器往父容器进行处理
  • 从视觉关系来说,从最底的界面往上层界面分发,再从上层界面往最底界面处理
分发机制

拿最顶层蓝色容器做例子

一、super

dispatchTouchEventonInterceptTouchEventonTouchEvent都是用super的情况,只会响应Down事件,因为没有人愿意分发,没有人愿意消费,导致流局

I/[Hensen]Yellow: ==dispatchTouchEvent: ACTION_DOWN
I/[Hensen]Yellow: ==onInterceptTouchEvent: ACTION_DOWN
I/[Hensen]Red: ==dispatchTouchEvent: ACTION_DOWN
I/[Hensen]Red: ==onInterceptTouchEvent: ACTION_DOWN
I/[Hensen]Blue: ==dispatchTouchEvent: ACTION_DOWN
I/[Hensen]Blue: ==onInterceptTouchEvent: ACTION_DOWN
I/[Hensen]Blue: ==onTouchEvent: ACTION_DOWN
I/[Hensen]Red: ==onTouchEvent: ACTION_DOWN
I/[Hensen]Yellow: ==onTouchEvent: ACTION_DOWN

二、dispatchTouchEvent

蓝色容器返回false,不愿意分发,导致蓝色无法继续处理事件,最终导致流局

I/[Hensen]Yellow: ==dispatchTouchEvent: ACTION_DOWN
I/[Hensen]Yellow: ==onInterceptTouchEvent: ACTION_DOWN
I/[Hensen]Red: ==dispatchTouchEvent: ACTION_DOWN
I/[Hensen]Red: ==onInterceptTouchEvent: ACTION_DOWN
I/[Hensen]Blue: ==dispatchTouchEvent: ACTION_DOWN(不愿意分发,蓝色无法处理其他事件)
I/[Hensen]Red: ==onTouchEvent: ACTION_DOWN
I/[Hensen]Yellow: ==onTouchEvent: ACTION_DOWN

蓝色容器返回true,愿意分发,事件正常传递,Move和Up两兄弟得到他的分发,要注意的是,愿意分发也代表着他消费掉了事件,不会再继续下发touch事件

I/[Hensen]Yellow: ==dispatchTouchEvent: ACTION_DOWN
I/[Hensen]Yellow: ==onInterceptTouchEvent: ACTION_DOWN
I/[Hensen]Red: ==dispatchTouchEvent: ACTION_DOWN
I/[Hensen]Red: ==onInterceptTouchEvent: ACTION_DOWN
I/[Hensen]Blue: ==dispatchTouchEvent: ACTION_DOWN(愿意分发,且在这里消费)
I/[Hensen]Yellow: ==dispatchTouchEvent: ACTION_MOVE
I/[Hensen]Yellow: ==onInterceptTouchEvent: ACTION_MOVE
I/[Hensen]Red: ==dispatchTouchEvent: ACTION_MOVE
I/[Hensen]Red: ==onInterceptTouchEvent: ACTION_MOVE
I/[Hensen]Blue: ==dispatchTouchEvent: ACTION_MOVE
...................(重复MOVE事件)
I/[Hensen]Yellow: ==dispatchTouchEvent: ACTION_UP
I/[Hensen]Yellow: ==onInterceptTouchEvent: ACTION_UP
I/[Hensen]Red: ==dispatchTouchEvent: ACTION_UP
I/[Hensen]Red: ==onInterceptTouchEvent: ACTION_UP
I/[Hensen]Blue: ==dispatchTouchEvent: ACTION_UP

三、onInterceptTouchEvent

蓝色容器返回false,不愿意拦截,导致事件没人管,回到最基本状态,最终导致流局

I/[Hensen]Yellow: ==dispatchTouchEvent: ACTION_DOWN
I/[Hensen]Yellow: ==onInterceptTouchEvent: ACTION_DOWN
I/[Hensen]Red: ==dispatchTouchEvent: ACTION_DOWN
I/[Hensen]Red: ==onInterceptTouchEvent: ACTION_DOWN
I/[Hensen]Blue: ==dispatchTouchEvent: ACTION_DOWN
I/[Hensen]Blue: ==onInterceptTouchEvent: ACTION_DOWN
I/[Hensen]Blue: ==onTouchEvent: ACTION_DOWN
I/[Hensen]Red: ==onTouchEvent: ACTION_DOWN
I/[Hensen]Yellow: ==onTouchEvent: ACTION_DOWN

蓝色容器返回true,愿意拦截,事件有人管了,但由于你其他方法返回super没有无人消费和无人分发,导致事件最终到拦截这里流局

I/[Hensen]Yellow: ==dispatchTouchEvent: ACTION_DOWN
I/[Hensen]Yellow: ==onInterceptTouchEvent: ACTION_DOWN
I/[Hensen]Red: ==dispatchTouchEvent: ACTION_DOWN
I/[Hensen]Red: ==onInterceptTouchEvent: ACTION_DOWN
I/[Hensen]Blue: ==dispatchTouchEvent: ACTION_DOWN
I/[Hensen]Blue: ==onInterceptTouchEvent: ACTION_DOWN
I/[Hensen]Blue: ==onTouchEvent: ACTION_DOWN
I/[Hensen]Red: ==onTouchEvent: ACTION_DOWN
I/[Hensen]Yellow: ==onTouchEvent: ACTION_DOWN

四、onTouchEvent

蓝色容器返回false,不愿意消费,导致事件没人管,回到最基本状态,最终导致流局

I/[Hensen]Yellow: ==dispatchTouchEvent: ACTION_DOWN
I/[Hensen]Yellow: ==onInterceptTouchEvent: ACTION_DOWN
I/[Hensen]Red: ==dispatchTouchEvent: ACTION_DOWN
I/[Hensen]Red: ==onInterceptTouchEvent: ACTION_DOWN
I/[Hensen]Blue: ==dispatchTouchEvent: ACTION_DOWN
I/[Hensen]Blue: ==onInterceptTouchEvent: ACTION_DOWN
I/[Hensen]Blue: ==onTouchEvent: ACTION_DOWN
I/[Hensen]Red: ==onTouchEvent: ACTION_DOWN
I/[Hensen]Yellow: ==onTouchEvent: ACTION_DOWN

蓝色容器返回true,愿意消费,事件有人消费了,你来多少事件我都消费,所以Move和Up两兄弟得到他的分发

I/[Hensen]Yellow: ==dispatchTouchEvent: ACTION_DOWN
I/[Hensen]Yellow: ==onInterceptTouchEvent: ACTION_DOWN
I/[Hensen]Red: ==dispatchTouchEvent: ACTION_DOWN
I/[Hensen]Red: ==onInterceptTouchEvent: ACTION_DOWN
I/[Hensen]Blue: ==dispatchTouchEvent: ACTION_DOWN
I/[Hensen]Blue: ==onInterceptTouchEvent: ACTION_DOWN
I/[Hensen]Blue: ==onTouchEvent: ACTION_DOWN
I/[Hensen]Yellow: ==dispatchTouchEvent: ACTION_MOVE
I/[Hensen]Yellow: ==onInterceptTouchEvent: ACTION_MOVE
I/[Hensen]Red: ==dispatchTouchEvent: ACTION_MOVE
I/[Hensen]Red: ==onInterceptTouchEvent: ACTION_MOVE
I/[Hensen]Blue: ==dispatchTouchEvent: ACTION_MOVE
I/[Hensen]Blue: ==onTouchEvent: ACTION_MOVE
...................(重复MOVE事件)
I/[Hensen]Yellow: ==dispatchTouchEvent: ACTION_UP
I/[Hensen]Yellow: ==onInterceptTouchEvent: ACTION_UP
I/[Hensen]Red: ==dispatchTouchEvent: ACTION_UP
I/[Hensen]Red: ==onInterceptTouchEvent: ACTION_UP
I/[Hensen]Blue: ==dispatchTouchEvent: ACTION_UP
I/[Hensen]Blue: ==onTouchEvent: ACTION_UP

同层级View嵌套

嵌套关系的处理市场已经非常多了,但是同层级View的处理还比较少

<RelativeLayout xmlns:android="http://schemas.android.com/apk/res/android"
    android:layout_width="match_parent"
    android:layout_height="match_parent">

    <com.hensen.touch.Yellow
        android:id="@+id/yellow"
        android:layout_width="match_parent"
        android:layout_height="match_parent"
        android:background="#ff0">
    </com.hensen.touch.Yellow>

    <com.hensen.touch.Red
        android:id="@+id/red"
        android:layout_width="match_parent"
        android:layout_height="match_parent"
        android:layout_margin="80dp"
        android:background="#f00">
    </com.hensen.touch.Red>

    <com.hensen.touch.Blue
        android:id="@+id/blue"
        android:layout_width="match_parent"
        android:layout_height="match_parent"
        android:layout_margin="120dp"
        android:background="#00f">
    </com.hensen.touch.Blue>
</RelativeLayout>
分发步骤
  • 从层级关系来说,从最上层的层级往下层层级界面分发(即从蓝色容器开始分发)
分发机制

拿最顶层蓝色容器做例子

一、super

事件从层级顶到下分发

I/[Hensen]Blue: ==dispatchTouchEvent: ACTION_DOWN
I/[Hensen]Blue: ==onInterceptTouchEvent: ACTION_DOWN
I/[Hensen]Blue: ==onTouchEvent: ACTION_DOWN
I/[Hensen]Red: ==dispatchTouchEvent: ACTION_DOWN
I/[Hensen]Red: ==onInterceptTouchEvent: ACTION_DOWN
I/[Hensen]Red: ==onTouchEvent: ACTION_DOWN
I/[Hensen]Yellow: ==dispatchTouchEvent: ACTION_DOWN
I/[Hensen]Yellow: ==onInterceptTouchEvent: ACTION_DOWN
I/[Hensen]Yellow: ==onTouchEvent: ACTION_DOWN

二、dispatchTouchEvent

蓝色容器返回false,不愿意分发,导致蓝色无法继续处理事件,最终导致蓝色的事件流局,继续往下传递

I/[Hensen]Blue: ==dispatchTouchEvent: ACTION_DOWN
I/[Hensen]Red: ==dispatchTouchEvent: ACTION_DOWN
I/[Hensen]Red: ==onInterceptTouchEvent: ACTION_DOWN
I/[Hensen]Red: ==onTouchEvent: ACTION_DOWN
I/[Hensen]Yellow: ==dispatchTouchEvent: ACTION_DOWN
I/[Hensen]Yellow: ==onInterceptTouchEvent: ACTION_DOWN
I/[Hensen]Yellow: ==onTouchEvent: ACTION_DOWN

蓝色容器返回true,愿意分发,事件正常传递,Move和Up两兄弟得到他的分发,要注意的是,愿意分发也代表着他消费掉了事件,不会再继续下发touch事件

I/[Hensen]Blue: ==dispatchTouchEvent: ACTION_DOWN
I/[Hensen]Blue: ==dispatchTouchEvent: ACTION_MOVE
...................(重复MOVE事件)
I/[Hensen]Blue: ==dispatchTouchEvent: ACTION_UP

三、onInterceptTouchEvent

蓝色容器返回false,不愿意拦截,顶层事件没人管,回到最基本状态,继续往下传递

I/[Hensen]Blue: ==dispatchTouchEvent: ACTION_DOWN
I/[Hensen]Blue: ==onInterceptTouchEvent: ACTION_DOWN
I/[Hensen]Blue: ==onTouchEvent: ACTION_DOWN
I/[Hensen]Red: ==dispatchTouchEvent: ACTION_DOWN
I/[Hensen]Red: ==onInterceptTouchEvent: ACTION_DOWN
I/[Hensen]Red: ==onTouchEvent: ACTION_DOWN
I/[Hensen]Yellow: ==dispatchTouchEvent: ACTION_DOWN
I/[Hensen]Yellow: ==onInterceptTouchEvent: ACTION_DOWN
I/[Hensen]Yellow: ==onTouchEvent: ACTION_DOWN

蓝色容器返回true,愿意拦截,顶层事件有人管了,但由于你其他方法返回super没有无人消费和无人分发,继续往下传递

I/[Hensen]Blue: ==dispatchTouchEvent: ACTION_DOWN
I/[Hensen]Blue: ==onInterceptTouchEvent: ACTION_DOWN
I/[Hensen]Blue: ==onTouchEvent: ACTION_DOWN
I/[Hensen]Red: ==dispatchTouchEvent: ACTION_DOWN
I/[Hensen]Red: ==onInterceptTouchEvent: ACTION_DOWN
I/[Hensen]Red: ==onTouchEvent: ACTION_DOWN
I/[Hensen]Yellow: ==dispatchTouchEvent: ACTION_DOWN
I/[Hensen]Yellow: ==onInterceptTouchEvent: ACTION_DOWN
I/[Hensen]Yellow: ==onTouchEvent: ACTION_DOWN

四、onTouchEvent

蓝色容器返回false,顶层事件不愿意消费,继续往下传递,回到最基本状态

I/[Hensen]Blue: ==dispatchTouchEvent: ACTION_DOWN
I/[Hensen]Blue: ==onInterceptTouchEvent: ACTION_DOWN
I/[Hensen]Blue: ==onTouchEvent: ACTION_DOWN
I/[Hensen]Red: ==dispatchTouchEvent: ACTION_DOWN
I/[Hensen]Red: ==onInterceptTouchEvent: ACTION_DOWN
I/[Hensen]Red: ==onTouchEvent: ACTION_DOWN
I/[Hensen]Yellow: ==dispatchTouchEvent: ACTION_DOWN
I/[Hensen]Yellow: ==onInterceptTouchEvent: ACTION_DOWN
I/[Hensen]Yellow: ==onTouchEvent: ACTION_DOWN

蓝色容器返回true,所有事件都被顶层吃完,传递不下去

I/[Hensen]Blue: ==dispatchTouchEvent: ACTION_DOWN
I/[Hensen]Blue: ==onInterceptTouchEvent: ACTION_DOWN
I/[Hensen]Blue: ==onTouchEvent: ACTION_DOWN
I/[Hensen]Blue: ==dispatchTouchEvent: ACTION_MOVE
I/[Hensen]Blue: ==onTouchEvent: ACTION_MOVE
I/[Hensen]Blue: ==dispatchTouchEvent: ACTION_MOVE
I/[Hensen]Blue: ==onTouchEvent: ACTION_MOVE
...................(重复MOVE事件)
I/[Hensen]Blue: ==dispatchTouchEvent: ACTION_UP
I/[Hensen]Blue: ==onTouchEvent: ACTION_UP

结语

嵌套层级提供了2种解题思路

  • 外部拦截法(父容器的拦截:父容器主动拦截onInterceptTouchEvent返回true
  • 内部拦截法(子容器的拦截:parent.requestDisallowInterceptTouchEvent(true)

同级层级这里我也提供两种个人的解题思路

  • 事件分发法:(在顶层容器中onTouchEvent在回调中,再调用同级View对象中view.onTouchEvent(event)
  • 遮罩法:将顶层容器View设置为不拦截,然后生成一层新的局部点击区域的View,盖在最顶层处理点击事件
  • 24
    点赞
  • 80
    收藏
    觉得还不错? 一键收藏
  • 打赏
    打赏
  • 20
    评论

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

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

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

许英俊潇洒

你的鼓励将是我创作的最大动力

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付:¥1
获取中
扫码支付

您的余额不足,请更换扫码支付或充值

打赏作者

实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

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

余额充值