Android View事件分发源码分析
今天通过源码分析下Android事件分发机制,分别从Activity、ViewGroup、View进行分析
Activity的事件分发
当点击屏幕,MetionEvent.MOVE_DOWND的时候,首先会调用dispatchTouchEvent(),其源码如下:
public boolean dispatchTouchEvent(MotionEvent ev) {
if (ev.getAction() == MotionEvent.ACTION_DOWN) {
onUserInteraction();
}
if (getWindow().superDispatchTouchEvent(ev)) {
return true;
}
return onTouchEvent(ev);
}
当按下操作的时候会调用onUserInteraction()方法,该方法进入发现是空实现,其翻译:
每当将按键、触摸或轨迹球事件发送到活动。如果您希望知道用户在活动运行时以某种方式与设备交互。此回调和@link onUserLeaveHint旨在帮助活动智能地管理状态栏通知;具体来说,帮助活动确定取消通知的适当时间
/**
* Called whenever a key, touch, or trackball event is dispatched to the
* activity.Implement this method if you wish to know that the user has
* interacted with the device in some way while your activity is running.
* This callback and {@link #onUserLeaveHint} are intended to help
* activities manage status bar notifications intelligently;
specifically,
* for helping activities determine the proper time to cancel a notfication.
*
* All calls to your activity's {@link #onUserLeaveHint} callback will
* be accompanied by calls to {@link #onUserInteraction}.This
* ensures that your activity will be told of relevant user activity such
* as pulling down the notification pane and touching an item there.
*
* Note that this callback will be invoked for the touch down action
* that begins a touch gesture, but may not be invoked for the touch-moved
* and touch-up actions that follow.
*
* @see #onUserLeaveHint()
*/
public void onUserInteraction() {
}
这
是一个
抽象类,其上面描述了,不需要开发人员去实现,但是、if (getWindow().superDispatchTouchEvent(ev))本质执行的是一个ViewGroup的dispatchTouchEvent方法(这个ViewGroup是Activity特有的root view,也就是id为content的FrameLayout布局) /**
* Used by custom windows, such as Dialog, to pass the touch screen event
* further down the view hierarchy. Application developers should
* not need to implement or call this.
*
*/
public abstract boolean superDispatchTouchEvent(MotionEvent event);
最后去调用onTouchEvent(ev),其内部实现如下:
public boolean onTouchEvent(MotionEvent event) {
if (mWindow.shouldCloseOnTouch(this, event)) {
finish();
return true;
}return false;
}
首先进入如下代码判断:
public boolean shouldCloseOnTouch(Context context, MotionEvent event) {
final boolean isOutside =
event.getAction() == MotionEvent.ACTION_DOWN && isOutOfBounds(context, event)
|| event.getAction() == MotionEvent.ACTION_OUTSIDE;
if (mCloseOnTouchOutside && peekDecorView() != null && isOutside) {
return true;
}
return false;
}
这里主要判断为按下并且是否在边界外,如果在就消费事件,返回true,分发结束,如果不在返回false,,onTouch也就返回false,activity层的事件分发结束,交给Viewgroup层继续分发,直到被消费
Viewgroup层事件分发
我们也从Viegroup的dispatchTouchEvent开始,代码有点长,分段看。
如下代码,调用了onInterceptTouchEvent(ev),获取事件是否被拦截了,如果拦截了,就将intercepted设置为 true
// 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;
}
如下代码,获取事件是否被取消,如果取消了,将canceled设置为true
// Check for cancelation.
final boolean canceled = resetCancelNextUpFlag(this)
|| actionMasked == MotionEvent.ACTION_CANCEL;
// Update list of touch targets for pointer down, if needed.
final boolean split = (mGroupFlags & FLAG_SPLIT_MOTION_EVENTS) != 0;
TouchTarget newTouchTarget = null;
如下判断,如果没被拦截,没被取消,则如果事件的目标是可访问性焦点,我们将其提供给,具有辅助功能焦点的视图,如果它不处理它,ViewGroup将事件分发给所有子视图,代码中可以看到,进行遍历子视图。
if (!canceled && !intercepted) {// If the event is targeting accessibility focus we give it to the
// view that has accessibility focus and if it does not handle it
// we clear the flag and dispatch the event to all children as usual.
// We are looking up the accessibility focused host to avoid keeping
// state since these events are very rare.
View childWithAccessibilityFocus = ev.isTargetAccessibilityFocus()
? findChildWithAccessibilityFocus() : null;
if (actionMasked == MotionEvent.ACTION_DOWN
|| (split && actionMasked == MotionEvent.ACTION_POINTER_DOWN)
|| actionMasked == MotionEvent.ACTION_HOVER_MOVE) {
final int actionIndex = ev.getActionIndex();
// always 0 for down
final int idBitsToAssign = split ? 1 << ev.getPointerId(actionIndex)
: TouchTarget.ALL_POINTER_IDS;
// Clean up earlier touch targets for this pointer id in case they
// have become out of sync.
removePointersFromTouchTargets(idBitsToAssign);
final int childrenCount = mChildrenCount;
if (newTouchTarget == null && childrenCount != 0) {
final float x = ev.getX(actionIndex);
final float y = ev.getY(actionIndex);
// Find a child that can receive the event.
// Scan children from front to back.
final ArrayList preorderedList = buildTouchDispatchChildList();
final boolean customOrder = preorderedList == null
&& isChildrenDrawingOrderEnabled();
final View[] children = mChildren;
for (int i = childrenCount - 1;
i >= 0;
i--) {
final int childIndex = getAndVerifyPreorderedIndex(
childrenCount, i, customOrder);
final View child = getAndVerifyPreorderedView(
preorderedList, children, childIndex);
// If there is a view that has accessibility focus we want it
// to get the event first and if not handled we will perform a
// normal dispatch. We may do a double iteration but this is
// safer given the timeframe.
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);
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);
}
if (preorderedList != null) preorderedList.clear();
}
再进入dispatchTransformedTouchEvent方法,首先判断事件是否被取消,如果没被取消,仅需往下走,判断新的焦点和旧的焦点是否在同一位置,如果在同一位,将事件分发给子view进行处理
private boolean dispatchTransformedTouchEvent(MotionEvent event, boolean cancel,
View child, int desiredPointerIdBits) {
final boolean handled;
// Canceling motions is a special case.We don't need to perform any transformations
// or filtering.The important part is the action, not the contents.
final int oldAction = event.getAction();
if (cancel || oldAction == MotionEvent.ACTION_CANCEL) {
event.setAction(MotionEvent.ACTION_CANCEL);
if (child == null) {
handled = super.dispatchTouchEvent(event);
} else {
handled = child.dispatchTouchEvent(event);
}
event.setAction(oldAction);
return handled;
}// Calculate the number of pointers to deliver.
final int oldPointerIdBits = event.getPointerIdBits();
final int newPointerIdBits = oldPointerIdBits & desiredPointerIdBits;
// If for some reason we ended up in an inconsistent state where it looks like we
// might produce a motion event with no pointers in it, then drop the event.
if (newPointerIdBits == 0) {
return false;
}// If the number of pointers is the same and we don't need to perform any fancy
// irreversible transformations, then we can reuse the motion event for this
// dispatch as long as we are careful to revert any changes we make.
// Otherwise we need to make a copy.
final MotionEvent transformedEvent;
if (newPointerIdBits == oldPointerIdBits) {
if (child == null || child.hasIdentityMatrix()) {
if (child == null) {
handled = super.dispatchTouchEvent(event);
} else {
final float offsetX = mScrollX - child.mLeft;
final float offsetY = mScrollY - child.mTop;
event.offsetLocation(offsetX, offsetY);
handled = child.dispatchTouchEvent(event);
event.offsetLocation(-offsetX, -offsetY);
}
return handled;
}
transformedEvent = MotionEvent.obtain(event);
} else {
transformedEvent = event.split(newPointerIdBits);
}// Perform any necessary transformations and dispatch.
if (child == null) {
handled = super.dispatchTouchEvent(transformedEvent);
} else {
final float offsetX = mScrollX - child.mLeft;
final float offsetY = mScrollY - child.mTop;
transformedEvent.offsetLocation(offsetX, offsetY);
if (! child.hasIdentityMatrix()) {
transformedEvent.transform(child.getInverseMatrix());
}handled = child.dispatchTouchEvent(transformedEvent);
}// Done.
transformedEvent.recycle();
return handled;
}
当按钮按下屏幕的时候,首先调用dispatchTouchEvent方法,接下来我们看下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;
}
该方法返回result,是一个boolean类型,通过上篇文章我们知道,根据返回的boolean类型,判断事件是否继续分发,返回true,时间继续分发,返回false,事件不再分发,那我们看下哪些地方返回了true吧。从代码可以看到,有三个地方返回了true:
第一个:当是滚动条拖动事件处理返回true
if ((mViewFlags & ENABLED_MASK) == ENABLED && handleScrollBarDragging(event)) {
result = true;
}
第二个:onTouch事件监听不为null,并且view可被点击,onTouch返回true表示该View被消费,false表示不被消费
ListenerInfo li = mListenerInfo;
if (li != null && li.mOnTouchListener != null
&& (mViewFlags & ENABLED_MASK) == ENABLED
&& li.mOnTouchListener.onTouch(this, event)) {
result = true;
}
public interface OnTouchListener {
/**
* Called when a touch event is dispatched to a view. This allows listeners to
* get a chance to respond before the target view.
*
* @param v The view the touch event has been dispatched to.
* @param event The MotionEvent object containing full information about
*the event.
* @return True if the listener has consumed the event, false otherwise.
*/
boolean onTouch(View v, MotionEvent event);
}
第三:onTouchEvent事件返回true,也会返回true
if (!result && onTouchEvent(event)) {
result = true;
}
接下来看看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();
final boolean clickable = ((viewFlags & CLICKABLE) == CLICKABLE
|| (viewFlags & LONG_CLICKABLE) == LONG_CLICKABLE)
|| (viewFlags & CONTEXT_CLICKABLE) == CONTEXT_CLICKABLE;
if ((viewFlags & ENABLED_MASK) == DISABLED) {
if (action == MotionEvent.ACTION_UP && (mPrivateFlags & PFLAG_PRESSED) != 0) {
setPressed(false);
}
mPrivateFlags3 &= ~PFLAG3_FINGER_DOWN;
// A disabled view that is clickable still consumes the touch
// events, it just doesn't respond to them.
return clickable;
}
if (mTouchDelegate != null) {
if (mTouchDelegate.onTouchEvent(event)) {
return true;
}
}if (clickable || (viewFlags & TOOLTIP) == TOOLTIP) {
switch (action) {
case MotionEvent.ACTION_UP:
mPrivateFlags3 &= ~PFLAG3_FINGER_DOWN;
if ((viewFlags & TOOLTIP) == TOOLTIP) {
handleTooltipUp();
}
if (!clickable) {
removeTapCallback();
removeLongPressCallback();
mInContextButtonPress = false;
mHasPerformedLongPress = false;
mIgnoreNextUpEvent = false;
break;
}
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)) {
performClickInternal();
}
}
}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:
if (event.getSource() == InputDevice.SOURCE_TOUCHSCREEN) {
mPrivateFlags3 |= PFLAG3_FINGER_DOWN;
}
mHasPerformedLongPress = false;
if (!clickable) {
checkForLongClick(0, x, y);
break;
}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:
if (clickable) {
setPressed(false);
}
removeTapCallback();
removeLongPressCallback();
mInContextButtonPress = false;
mHasPerformedLongPress = false;
mIgnoreNextUpEvent = false;
mPrivateFlags3 &= ~PFLAG3_FINGER_DOWN;
break;
case MotionEvent.ACTION_MOVE:
if (clickable) {
drawableHotspotChanged(x, y);
}// Be lenient about moving outside of buttons
if (!pointInView(x, y, mTouchSlop)) {
// Outside button
// Remove any future long press/tap checks
removeTapCallback();
removeLongPressCallback();
if ((mPrivateFlags & PFLAG_PRESSED) != 0) {
setPressed(false);
}
mPrivateFlags3 &= ~PFLAG3_FINGER_DOWN;
}
break;
}return true;
}return false;
}
1、首先获取clickable的值,为点击事件或者长按事件或者是上下文点击事件返回true,再判断如果该View被禁止,进行点击事件,仍然会消费touch event,但是不会返回结果。
2、接着判断是否是touchDelegate的事件处理,如果TouchDelegate的onTouchEvent处理返回true,也会返回true
3、接下来看下MotionEvent.ACTION_UP里面实现,主要看下如下段,
文章图片
文章图片
文章图片
文章图片
首先通知调用notifyAutofillManagerOnClick()方法,告知自动管理器处理点击事件,接着通过setOnClickListener()为控件View注册1个点击事件,调用了点击按钮的声音,还给mOnClickListener变量赋值(即不为空,则会往下回调onClick() & performClick()返回true,即调用onTouch事件要调用performClick事件,当这些执行完才能执行我们常见的onClick事件,这样分发事件就结束了!onTouch() ->> onTouchEvent() ->> performClick() ->> onClick()
总结:Android事件分发,从Activity——》ViewGrop——》View,ViewGrop相当于是容器的父类,例如Linearlayout、RelativeLayout、ListView等容器的父类,而ViewGrop又集成于View,TextView、EdietView、Button的顶级父类都是view。
Activity事件没被消费,就向ViewGrop层分发,ViewGroup事件没被消费或拦截,如果ViewGroup里面还套嵌了ViewGroup
接着向其套嵌的ViewGroup分发,套嵌的ViewGroup再向容器里面的view进行分发。
每个Activity事件处理流程:dispatchTouchEvent()——》onTouch()——》onTouchEvent()
每个ViewGroup事件处理流程:dispatchTouchEvent()——》onInterceptTouchEvent()(拦截器)——》onTouch()——》onTouchEvent() ——》performClick()——》 onClick()
每个view事件处理流程:dispatchTouchEvent()——》onTouch()——》onTouchEvent() ——》performClick()——》 onClick()
假如 一个Activity里有一个LinearLayout布局,布局里面有一个Button,其点击事件事件分发流程如下:
Activity()的dispatchTouchEvent()——》LinearLayout的dispatchTouchEvent()——》LinearLayout的onInterceptTouchEvent()(拦截器)——》Button的dispatchTouchEvent()——>Button的onTouchEvent() )
——》LinearLayout的onTouchEvent() ——》Activity的onTouchEvent()——》performClick()——》onClick()
如下图如果事件未被消费或者未被拦截,将呈现U字型传递
【Android View事件分发源码分析】
文章图片
推荐阅读
- Android学习|Android 11 保存文件到外部存储,并分享文件
- Android中的进程名和线程名
- 如何维护一个巨大的Android项目呢(阿里大佬分享的高级Android|如何维护一个巨大的Android项目呢?阿里大佬分享的高级Android 组件化实战,你确定不看看)
- Android安卓进阶之——一文带你了解抓包和反抓包
- ASP.NET|ASP.NET MVC中_ViewStart.cshtml作用介绍
- ASP.NET|ASP.NET MVC中Controller控制器向View视图传值的几种方式
- 移动开发|谷歌为什么要对Android的开源严防死守()
- Android 系统 Bar 沉浸式完美兼容方案
- Android Handler面试总结
- 欢迎体验 | Android 13 开发者预览版 2