The Android FW event model is a little confusing. Since we're generally limited to a single listener, I've run into a couple issues I'm not sure how to handle correctly. In both cases, I was able to eventually get the net result to work, but generally with some hacky workarounds. I wonder if I'm missing some fundamental concepts. The first and most common example would be a "widget" with default touch event handler, yet still accept other listeners normally. E.g., let's say I have a class that has several views. On the main container (layout), I either add an onTouchListener or override onTouchEvent to perform visual feedback while the finger is down. If I return false, ACTION_UP doesn't fire since it didn't handle ACTION_DOWN. If I return true, ACTION_UP fires, but listeners assigned with setOnClickListener never fire, since the event was already consumed. What's the best practice here?
-- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
