My understanding is that it actually goes the other direction. The Child views get their event triggered first (sort of). The root view get's it's dispatchTouchEvent()
called, which propagates the event down to the children's onTouchEvent()
, and then, depending on whether they return true or false, the parent's onTouchEvent()
is called.
The normal solution for intercepting things like this is to override dispatchTouchEvent(MotionEvent ev)
in one's activity like so:
@Override
public boolean dispatchTouchEvent (MotionEvent ev) {
// Do your calcluations
return super.dispatchTouchEvent(ev);
}
The documentation for this one is here. Note that you can also override that method in any ViewGroup
(such as a FrameLayout
, etc)
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…