Once a down is dispatched to a view, that view remains the target of pointer events until the following up. The only exception to this is that a parent can cancel the current target and start handling the pointer events itself.
On Tue, Dec 16, 2008 at 3:03 PM, Patrick <[email protected]> wrote: > > I have a number of views on screen (Buttons actually, but it could > change if needed). I want to know which one the user's finger is on > top of. I setup a touch listener on each view, and then monitor for > MotionEvent.ACTION_DOWN and MotionEvent.ACTION_MOVE. > > I get both just fine, except that the MotionEvent.ACTION_MOVE I get > always refers to the view that originally got the > MotionEvent.ACTION_DOWN, not the view the finger is now on top of. > > Is there a way to "reset" the touch state, so that the OS figures out > which view the user is on? I don't want to force the user to have to > lift and re-hit whenever he changes which button he's on top of. > > > > -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support. All such questions should be posted on public forums, where I and others can see and answer them. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
