Android事件分发源码浅读及总结 -- View

最近把事件分发的知识复习了一遍，这里先对View部分做个小小的总结吧。关于这部分的内容，我主要也是跟着博客及书本学习的。书的话推荐《Android开发艺术探索》，博客推荐这个：http://blog.csdn.net/yanbober/article/details/45887547，工匠大神总结的非常清晰~~。

1. 事件分发介绍

事件分发，其实就是对MotionEvent的分发。用户手指按下、滑动、抬起，分别对应ACTION_DOWN、一系列的

ACTION_MOVE、和ACTION_UP。正常情况下，每个事件由最外层的ViewGroup层层分发至内部的View。

关于MotionEvent的详解，可以参考下面这篇文章：

http://www.gcssloop.com/customview/motionevent

 

2. View的dispatchTouchEvent方法

事件分发到View时，首先触发的就是View的dispatchTouchEvent方法，源码如下：

 

    public boolean dispatchTouchEvent(MotionEvent event) {
        // If the event should be handled by accessibility focus first.
        if (event.isTargetAccessibilityFocus()) {
            // We don't have focus or no virtual descendant has it, do not handle the event.
            if (!isAccessibilityFocusedViewOrHost()) {
                return false;
            }
            // We have focus and got the event, then use normal event dispatch.
            event.setTargetAccessibilityFocus(false);
        }

        boolean result = false;

        if (mInputEventConsistencyVerifier != null) {
            mInputEventConsistencyVerifier.onTouchEvent(event, 0);
        }

        final int actionMasked = event.getActionMasked();
        if (actionMasked == MotionEvent.ACTION_DOWN) {
            // Defensive cleanup for new gesture
            stopNestedScroll();
        }

        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;
            }
        }

        if (!result && mInputEventConsistencyVerifier != null) {
            mInputEventConsistencyVerifier.onUnhandledEvent(event, 0);
        }

        // Clean up after nested scrolls if this is the end of a gesture;
        // also cancel it if we tried an ACTION_DOWN but we didn't want the rest
        // of the gesture.
        if (actionMasked == MotionEvent.ACTION_UP ||
                actionMasked == MotionEvent.ACTION_CANCEL ||
                (actionMasked == MotionEvent.ACTION_DOWN && !result)) {
            stopNestedScroll();
        }

        return result;
    }

代码很长，抓住关键点即可。第24行，if (onFilterTouchEventForSecurity(event))，判断View是否被遮挡，随后第29行，定义了一个ListenerInfo的局部变量li，ListenerInfo是View的静态内部类，它里面定义了一堆关于View的xxxListener的变量，用于保存我们给View设置的各种监听。比如我们通过setOnTouchListener给View设置了一个监听，其实在setOnTouchListener方法内部，这个Listener就被赋值给了ListenerInfo的mOnTouchListener变量，相关代码就不贴了，很简单的。

 

 

随后 if (li != null && li.mOnTouchListener != null && (mViewFlags & ENABLED_MASK) == ENABLED && li.mOnTouchListener.onTouch(this, event))，这个判断语句是重点。首先li肯定不为null，li.mOnTouchListener，这个就是我们调用setOnTouchListener给View设置的OnTouchListener，如果调用了，那li.mOnTouchListener也不为null。接下来，位运算判断view是否是enabled的，如果enable，则继续走到li.mOnTouchListener.onTouch，这就是在调用我们给view设置的OnTouchListener的onTouch方法了。

 

如果onTouch方法返回true，则result就是true，第36行里onTouchEvent就不会得到执行；如果onTouch返回false，则result为false，第36行里onTouchEvent就可以得到执行。接下来我们会看到，我们平时给view设置的OnClickListener，就是在onTouchEvent调用的。

 

通过对以上dispatchTouchEvent方法的分析，可以得出以下几点：

1. 如果对控件设置了onTouchListener，则先执行onTouch，若onTouch返回true，则dispatchTouchEvent方法直接返回true，不会执行onTouchEvent；若onTouch返回false，则onTouchEvent得到执行。

2. 如果控件是disabled，则onTouch方法不管有没有设置，都不会得到执行。而onTouchEvent可以执行。

3. 只要onTouchEvent方法得到执行，则dispatchTouchEvent返回值与onTouchEvent返回值一致。

 

3. View的onTouchEvent方法

接下来，我们看onTouchEvent的源码：

    public boolean onTouchEvent(MotionEvent event) {
        final float x = event.getX();
        final float y = event.getY();
        final int viewFlags = mViewFlags;
        final int action = event.getAction();

        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 (mTouchDelegate != null) {
            if (mTouchDelegate.onTouchEvent(event)) {
                return true;
            }
        }

        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) {
                        // take focus if we don't have it already and we should in
                        // touch mode.
                        boolean focusTaken = false;
                        if (isFocusable() && isFocusableInTouchMode() && !isFocused()) {
                            focusTaken = requestFocus();
                        }

                        if (prepressed) {
                            // The button is being released before we actually
                            // showed it as pressed.  Make it show the pressed
                            // state now (before scheduling the click) to ensure
                            // the user sees it.
                            setPressed(true, x, y);
                       }

                        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();
                                }
                            }
                        }

                        if (mUnsetPressedState == null) {
                            mUnsetPressedState = new UnsetPressedState();
                        }

                        if (prepressed) {
                            postDelayed(mUnsetPressedState,
                                    ViewConfiguration.getPressedStateDuration());
                        } else if (!post(mUnsetPressedState)) {
                            // If the post failed, unpress right now
                            mUnsetPressedState.run();
                        }

                        removeTapCallback();
                    }
                    mIgnoreNextUpEvent = false;
                    break;

                case MotionEvent.ACTION_DOWN:
                    mHasPerformedLongPress = false;

                    if (performButtonActionOnTouchDown(event)) {
                        break;
                    }

                    // Walk up the hierarchy to determine if we're inside a scrolling container.
                    boolean isInScrollingContainer = isInScrollingContainer();

                    // For views inside a scrolling container, delay the pressed feedback for
                    // a short period in case this is a scroll.
                    if (isInScrollingContainer) {
                        mPrivateFlags |= PFLAG_PREPRESSED;
                        if (mPendingCheckForTap == null) {
                            mPendingCheckForTap = new CheckForTap();
                        }
                        mPendingCheckForTap.x = event.getX();
                        mPendingCheckForTap.y = event.getY();
                        postDelayed(mPendingCheckForTap, ViewConfiguration.getTapTimeout());
                    } else {
                        // Not inside a scrolling container, so show the feedback right away
                        setPressed(true, x, y);
                        checkForLongClick(0, x, y);
                    }
                    break;

                case MotionEvent.ACTION_CANCEL:
                    setPressed(false);
                    removeTapCallback();
                    removeLongPressCallback();
                    mInContextButtonPress = false;
                    mHasPerformedLongPress = false;
                    mIgnoreNextUpEvent = false;
                    break;

                case MotionEvent.ACTION_MOVE:
                    drawableHotspotChanged(x, y);

                    // Be lenient about moving outside of buttons
                    if (!pointInView(x, y, mTouchSlop)) {
                        // Outside button
                        removeTapCallback();
                        if ((mPrivateFlags & PFLAG_PRESSED) != 0) {
                            // Remove any future long press/tap checks
                            removeLongPressCallback();

                            setPressed(false);
                        }
                    }
                    break;
            }

            return true;
        }

        return false;
    }

代码很长。。。继续抓重点吧。。。7~16行可知，如果view是disabled且clickable，则直接返回true；如果disabled且disclickable，则直接返回false。23行的if语句可知，如果viewenable但disclickable，则直接返回false。如果if语句满足，则进入一个switch中，对event进行处理，对于ACTION_DOWN、MOVE、CANCEL，主要做了一些位运算和标志位的操作，对于ACTION_UP，我们可以看到第57行，post一个在UI线程执行的Runnable，这个Runnable里面其实就是执行performClick方法：

public boolean performClick() {
        final boolean result;
        final ListenerInfo li = mListenerInfo;
        if (li != null && li.mOnClickListener != null) {
            playSoundEffect(SoundEffectConstants.CLICK);
            li.mOnClickListener.onClick(this);
            result = true;
        } else {
            result = false;
        }

        sendAccessibilityEvent(AccessibilityEvent.TYPE_VIEW_CLICKED);
        return result;
    }

4~7行可知，如果我们给view设置了OnClickListener，那么onClick方法就会得到执行。至此，我们就知道，原来平时常用的点击事件监听，其实是在View的onTouchEvent方法里，ACTION_UP的时候得到调用的~

 

 

至此，我们对View的事件分发过程，算是整理清楚了。下一篇将对ViewGroup的分发做个整理~~