android的事件分发处理流程
来源:互联网 发布:世界核武国家 知乎 编辑:程序博客网 时间:2024/06/05 20:14
大家好,最近在学习android,了解下事件的分发机制。一次触屏,系统会产生ACTION_DOWN事件,抬起手指又会产生ACTION_UP事件,中途你移动了手指又会产生很多ACTION_MOVE事件。为了简单,我们先不考虑ACTION_MOVE。当按下手指时,产生ACTION_DOWN事件,这个事件会来到最顶层的ViewGroup,由他来进行分发,具体处理过程在ViewGroup的dispatchTouchEvent函数里。
@Override public boolean dispatchTouchEvent(MotionEvent ev) { if (mInputEventConsistencyVerifier != null) { mInputEventConsistencyVerifier.onTouchEvent(ev, 1); } // If the event targets the accessibility focused view and this is it, start // normal event dispatch. Maybe a descendant is what will handle the click. if (ev.isTargetAccessibilityFocus() && isAccessibilityFocusedViewOrHost()) { ev.setTargetAccessibilityFocus(false); } boolean handled = false; if (onFilterTouchEventForSecurity(ev)) { final int action = ev.getAction(); final int actionMasked = action & MotionEvent.ACTION_MASK; // Handle an initial down. if (actionMasked == MotionEvent.ACTION_DOWN) { // Throw away all previous state when starting a new touch gesture. // The framework may have dropped the up or cancel event for the previous gesture // due to an app switch, ANR, or some other state change. cancelAndClearTouchTargets(ev); resetTouchState(); } // 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; } // If intercepted, start normal event dispatch. Also if there is already // a view that is handling the gesture, do normal event dispatch. if (intercepted || mFirstTouchTarget != null) { ev.setTargetAccessibilityFocus(false); } // 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; boolean alreadyDispatchedToNewTouchTarget = false; if (!canceled && !intercepted) { // If the event is targeting accessiiblity 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<View> 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(); } if (newTouchTarget == null && mFirstTouchTarget != null) { // Did not find a child to receive the event. // Assign the pointer to the least recently added target. newTouchTarget = mFirstTouchTarget; while (newTouchTarget.next != null) { newTouchTarget = newTouchTarget.next; } newTouchTarget.pointerIdBits |= idBitsToAssign; } } } // Dispatch to touch targets. if (mFirstTouchTarget == null) { // No touch targets so treat this as an ordinary view. handled = dispatchTransformedTouchEvent(ev, canceled, null, TouchTarget.ALL_POINTER_IDS); } else { // Dispatch to touch targets, excluding the new touch target if we already // dispatched to it. Cancel touch targets if necessary. TouchTarget predecessor = null; TouchTarget target = mFirstTouchTarget; while (target != null) { final TouchTarget next = target.next; if (alreadyDispatchedToNewTouchTarget && target == newTouchTarget) { handled = true; } else { final boolean cancelChild = resetCancelNextUpFlag(target.child) || intercepted; if (dispatchTransformedTouchEvent(ev, cancelChild, target.child, target.pointerIdBits)) { handled = true; } if (cancelChild) { if (predecessor == null) { mFirstTouchTarget = next; } else { predecessor.next = next; } target.recycle(); target = next; continue; } } predecessor = target; target = next; } } // Update list of touch targets for pointer up or cancel, if needed. if (canceled || actionMasked == MotionEvent.ACTION_UP || actionMasked == MotionEvent.ACTION_HOVER_MOVE) { resetTouchState(); } else if (split && actionMasked == MotionEvent.ACTION_POINTER_UP) { final int actionIndex = ev.getActionIndex(); final int idBitsToRemove = 1 << ev.getPointerId(actionIndex); removePointersFromTouchTargets(idBitsToRemove); } } if (!handled && mInputEventConsistencyVerifier != null) { mInputEventConsistencyVerifier.onUnhandledEvent(ev, 1); } return handled; }
我这里只讲下代码的逻辑,可自己去研究代码。
ViewGroup循环遍历它的每个子view,调用子view的dispatchTouchEvent,该子view又调用它自己的子view的dispatchTouchEvent,就这样一层一层的调用下去。记住,只有ACTION_DOWN的情况下ViewGroup才会遍历每个子view,它的目的是确定后续的事件我应该交给我的子view中的哪个view,即确定newTouchTarget。
当某个子view的dispatchTouchEvent返回了true,就是告诉父view,我要处理这次事件,父view也就会终止遍历,同时父view的newTouchTarget就指向了该子view。
举个例子:ViewGroup1里包含了ViewGroup2,ViewGroup2里包含了ViewGroup3,ViewGroup3里包含了ViewGroup4,ViewGroup4包含了一个Button。当点击Button时(手指先别抬起),会进入到ViewGroup4的dispatchTouchEvent,然后调用Button的dispatchTouchEvent。Button的dispatchTouchEvent会返回true,回到上一层,ViewGroup4的dispatchTouchEvent也会返回true,ViewGroup3的dispatchTouchEvent也会返回true,以此类推。 最后的结果是:ViewGroup1的newTouchTarget指向的是ViewGroup2,ViewGroup2的newTouchTarget指向的是ViewGroup3,ViewGroup3的newTouchTarget指向的是ViewGroup4,ViewGroup4的newTouchTarget指向的是Button。
当手指抬起来,产生了ACTION_UP事件,还是上面的那个例子,ViewGroup1会看自己的newTouchTarget有没有值,有! 于是它就把事件给ViewGroup2处理。ViewGroup2也看看自己的newTouchTarget有没有值,这样就来到ViewGroup4,ViewGroup4发现自己的newTouchTarget为Button,就把事件给Button了,于是我们的OnClick就执行了。
- android的事件分发处理流程
- 写一遍加深记忆 Android的事件分发处理流程
- Android中事件的分发与处理流程
- 【Android TV】按键事件KeyEvent的分发处理流程解析
- Android View 事件分发处理流程
- 浅谈android 点击事件分发处理流程
- android事件分发流程
- Android事件分发流程
- android 事件分发流程
- Android事件分发流程
- Android事件分发流程
- Android事件分发,拦截的流程梳理
- Android View的事件分发流程总结
- Android touch事件的分发流程
- Android Tv 中的按键事件 KeyEvent 分发处理流程
- Android 触摸事件的分发与处理流程:onInterceptTouchEvent和onTouchEvent
- android触摸事件的分发和处理
- Android触摸事件的分发处理
- 分布式锁
- 嵌入式视频处理考虑(一)
- 添加依赖
- 12. 机器学习基石-How can Machine Learn Better?
- kali linux shadowssock
- android的事件分发处理流程
- Unable to require openssl, install OpenSSL and rebuild ruby (preferred) or use non-HTTPS sources
- 【异常】执行yum install lrzsz 报错
- iOS_校验手机号
- 使用Maven和WinSCP命令自动打War包上传
- 叉姐200题
- php yii2跑数出现mysql-gone-away-2006解决
- 苹果匠艺:乔布斯身边的天才
- JVM_8_内存分配与回收策略