一步步探索學習Android Touch事件分發傳遞機制（三）
前言
該系列文章分三篇：java
- 一步步探索學習Android Touch事件分發傳遞機制（一） 經過寫demo打Log，以ACTION_DOWN事件爲例，完整了解整個Android Touch事件分發傳遞機制。
- 一步步探索學習Android Touch事件分發傳遞機制（二） 探索了ACTION_MOVE和ACTION_UP事件的分發傳遞規律。
- 一步步探索學習Android Touch事件分發傳遞機制（三） 即本篇，將經過Android源碼分析，從本質上認識Android Touch事件分發傳遞機制。
1. dispatchTouchEvent()方法源碼分析
1.1 Activity的dispatchTouchEvent()方法
- 源碼：
/** * Called to process touch screen events. You can override this to * intercept all touch screen events before they are dispatched to the * window. Be sure to call this implementation for touch screen events * that should be handled normally. * * @param ev The touch screen event. * * @return boolean Return true if this event was consumed. */
public boolean dispatchTouchEvent(MotionEvent ev) {
if (ev.getAction() == MotionEvent.ACTION_DOWN) {
//當判斷是ACTION_DOWN事件，回調onUserInteraction()
onUserInteraction();
}
if (getWindow().superDispatchTouchEvent(ev)) {
//getWindow（）方法拿到的是PhoneWindow的實例
return true;
}
//若是沒有找到消費該事件的子View，最終會交給Activity的onTouchEvent()處理
return onTouchEvent(ev);
}
複製代碼
- 分析：
-
該方法首先判斷傳遞進來的是否是一個ACTION_DOWN事件，if 是，就觸發一個叫作 onUserInteraction()的回調方法。app
-
onUserInteraction()方法在Activity.java中是個空實現。開發者能夠在須要的時候重寫它，好比用於判斷是否是用戶開始作與屏幕交互的事情了。ide
-
而後，判斷調用了getWindow().superDispatchTouchEvent(ev)。getWindow()拿到的是PhoneWindow的實例。源碼分析
-
這裏須要簡單說明一下Android窗口結構： 佈局
-
繼續看源碼，看看PhoneWindow.java中的superDispatchTouchEvent(ev)方法。post
@Override public boolean superDispatchTouchEvent(MotionEvent event) { return mDecor.superDispatchTouchEvent(event); } 複製代碼 -
能夠看到，這個方法內部又去調用了DecorView的superDispatchTouchEvent(ev)方法。學習
-
一路這麼調用，DecorView實際上是FrameLayout的子類，它沒重寫這個方法，因此最後調用到了ViewGroup的dispatchTouchEvent()方法。ui
-
1.2 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;
}
複製代碼
-
分析：this
-
這個方法的代碼邏輯比較多，有兩百多行。咱們去繁就簡，理出主要的邏輯就行，畢竟咱們只關心Touch事件的流向和處理邏輯。spa
-
首先來看一下，ViewGroup的dispatchTouchEvent()方法首先是要判斷該事件本身要不要攔截下來本身處理。
// 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; } 複製代碼 -
這裏面咱們看到一個很關鍵的boolean變量***disallowIntercept***，這個變量是控制是否是不容許父控件去攔截該事件的，取值是看mGroupFlags的取值。
這裏面涉及到一個方法：***requestDisallowInterceptTouchEvent()***方法。這個方法肯定mGroupFlags的取值，控制請求父佈局不攔截該事件，而是交給本身去作處理。這個方法在處理滑動衝突等場景時常常用到。但在這裏爲了整個源碼分析的邏輯簡潔清晰，再也不具體分析該方法的代碼。
-
還有你們能夠注意到一個判斷條件： ***if (actionMasked == MotionEvent.ACTION_DOWN|| mFirstTouchTarget != null)***，也就是說ViewGroup去判斷這個事件該不應去攔截，首先是這個事件得是ACTION_DOWN事件或者該事件的mFirstTouchTarget（目標子View）是不爲空的纔會考慮要不要攔截。
-
這說明mFirstTouchTarget爲空的狀況下，ACTION_MOVE和ACTION_UP事件是不會通過這個攔截判斷的，而是直接intercepted = true表示事件被直接攔截掉。這一點恰好印證了我在一步步探索學習Android Touch事件分發傳遞機制（二）中提到的ACTION_MOVE和ACTION_UP事件的分發規律。
-
那麼mFirstTouchTarget（目標子View）這個變量究竟是什麼呢？何時會爲空呢？
-
能夠看到ViewGroup的dispatchTouchEvent()方法的後續代碼，是一個for循環：
... 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. } ... 複製代碼-
這個for循環一個一個的遍歷子View，尋找看事件的發生座標在哪一個View的範圍中，若是找到了，就設置mFirstTouchTarget爲child,而且把alreadyDispatchedToNewTouchTarget設置爲true。
-
那麼事件最終交給本身處理仍是目標子View（mFirstTouchTarget）處理？
-
很簡單，通過上面的分析能夠知道，若是遍歷完以後mFirstTouchTarget不爲null，就傳給mFirstTouchTarget（目標子View）處理；若是爲null，就本身消費掉。
-
那其實不論是給目標子View處理仍是本身處理，都會跑到View的dispatchTouchEvent()方法。看源碼能夠知道，當mFirstTouchTarget爲null的時候，ViewGoup會調用super.dispatchTouchEvent(event),畢竟ViewGroup本質上是View的子類，因此其實ViewGroup調用的仍是View的dispatchTouchEvent()方法。那麼咱們下面分析View的dispatchTouchEvent()方法。
-
1.3 View的dispatchTouchEvent()方法
- 源碼：
/** * Pass the touch screen motion event down to the target view, or this * view if it is the target. * * @param event The motion event to be dispatched. * @return True if the event was handled by the view, false otherwise. */ 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; } 複製代碼 -
-
分析：
-
代碼量相對於ViewGroup的dispatchTouchEvnet()方法來講少不少。
-
主要是首先判斷這個View自己有沒有設置OnTouchListener監聽，若是有，就直接跑去調用該接口下的onTouch()方法。該方法若是return true,這事件就是被消費掉了。return false,事件仍是會傳回給onTouchEvent()方法。
注意：值得注意的是，ViewGroup自己並無重寫View的onTouchEvnet()方法，因此這裏若是回傳，也是調用的父類View.java的onTouchEvent()方法。
-
2. onTouchEvent()方法源碼分析
2.1 Activity的onTouchEvent()方法
- 源碼：
/** * Called when a touch screen event was not handled by any of the views * under it. This is most useful to process touch events that happen * outside of your window bounds, where there is no view to receive it. * * @param event The touch screen event being processed. * * @return Return true if you have consumed the event, false if you haven't. * The default implementation always returns false. */
public boolean onTouchEvent(MotionEvent event) {
if (mWindow.shouldCloseOnTouch(this, event)) {
finish();
return true;
}
return false;
}
複製代碼
-
分析：
-
這個方法代碼不多，默認Activity的onTouchEvent()方法是返回false的，也就是說默認不處理觸摸事件。
-
只有在PhoneWindow的shouldCloseOnTouch（）方法返回true纔會處理觸摸事件，直接finish整個Activity.
-
2.2 View的onTouchEvent()方法
前面說了，ViewGroup沒有重寫View的onTouchEvent()方法，因此繼承VIewGroup時，調用的仍是View的onTouchEvent()。
- 源碼：
/** * Implement this method to handle touch screen motion events. * <p> * If this method is used to detect click actions, it is recommended that * the actions be performed by implementing and calling * {@link #performClick()}. This will ensure consistent system behavior, * including: * <ul> * <li>obeying click sound preferences * <li>dispatching OnClickListener calls * <li>handling {@link AccessibilityNodeInfo#ACTION_CLICK ACTION_CLICK} when * accessibility features are enabled * </ul> * * @param event The motion event. * @return True if the event was handled, false otherwise. */
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)) {
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:
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;
}
複製代碼
-
分析：
-
代碼一樣很長，那麼咱們只去理清主要的邏輯。
-
當事件傳遞到該方法處，首先會判斷這個View是否是enabled狀態，是否是clickable狀態。
-
而後會根據Touch事件的類型作出不一樣的響應。好比View接收到Down事件和up事件等時候的表現效果。
注意：注意到一段比較重要的代碼
if (!post(mPerformClick)) { performClick(); }這段代碼在判斷是up事件以後調用了performClick()方法，這個方法回去回調onClickListener接口裏面的onClick()方法。 這結合前面dispatchTouchEvent()方法中ACTION_DOWN事件會去調用onTouch，可見onTouch比onClick優先。 -
3. onInterceptTouchEvent()方法源碼分析
只有ViewGroup有onInterceptTouchEvent()方法
- 源碼：
public boolean onInterceptTouchEvent(MotionEvent ev) {
if (ev.isFromSource(InputDevice.SOURCE_MOUSE)
&& ev.getAction() == MotionEvent.ACTION_DOWN
&& ev.isButtonPressed(MotionEvent.BUTTON_PRIMARY)
&& isOnScrollbarThumb(ev.getX(), ev.getY())) {
return true;
}
return false;
}
複製代碼
-
分析：
-
這個方法默認是返回false，表示不攔截觸摸事件的
-
只有在 ev.isFromSource(InputDevice.SOURCE_MOUSE) && ev.getAction() == MotionEvent.ACTION_DOWN && ev.isButtonPressed(MotionEvent.BUTTON_PRIMARY) && isOnScrollbarThumb(ev.getX(), ev.getY()) 這麼多條件同時成立時纔會攔截。
-
-
有須要的話，好比處理滑動衝突的時候，能夠重寫該方法，retrun true，攔截觸摸事件。
注：【轉載請註明，問題可提問，喜歡可收藏分享，博客持續更新，歡迎關注】
相關文章
- 1. 一步步探索學習Android Touch事件分發傳遞機制（一）
- 2. 一步步探索學習Android Touch事件分發傳遞機制（二）
- 3. android開發：探索學習Android Touch事件分發傳遞機制（一）
- 4. Android Touch事件分發機制學習
- 5. （轉）Android Touch事件傳遞機制
- 6. Android Touch事件傳遞機制
- 7. Android touch 事件傳遞機制
- 8. Android中Touch事件的傳遞機制
- 9. Android Touch事件傳遞機制詳解
- 10. Android Touch事件傳遞機制解析
- 更多相關文章...
- • 我們已經學習了 SQL，下一步學習什麼呢？ - SQL 教程
- • 您已經學習了 XML Schema，下一步學習什麼呢？ - XML Schema 教程
- • 漫談MySQL的鎖機制
- • Kotlin學習（一）基本語法
相關標籤/搜索
每日一句
-
每一个你不满意的现在，都有一个你没有努力的曾经。
最新文章
- 1. Duang!超快Wi-Fi來襲
- 2. 機器學習-補充03 神經網絡之**函數(Activation Function)
- 3. git上開源maven項目部署 多module maven項目（多module maven+redis+tomcat+mysql）後臺部署流程學習記錄
- 4. ecliple-tomcat部署maven項目方式之一
- 5. eclipse新導入的項目經常可以看到「XX cannot be resolved to a type」的報錯信息
- 6. Spark RDD的依賴於DAG的工作原理
- 7. VMware安裝CentOS-8教程詳解
- 8. YDOOK：Java 項目 Spring 項目導入基本四大 jar 包 導入依賴，怎樣在 IDEA 的項目結構中導入 jar 包 導入依賴
- 9. 簡單方法使得putty（windows10上）可以免密登錄樹莓派
- 10. idea怎麼用本地maven
歡迎關注本站公眾號,獲取更多信息
相關文章