yi, doing that will disable all normal touch event dispatching for
that view and any of its children. It's really rare that you should
override a dispatch method, especially doing so and never calling
through to the super class.
The correct thing is almost always to override onTouchEvent().
Rohit
On Oct 31, 1:05 pm, Rohit Mordani <[EMAIL PROTECTED]> wrote:
> In addition you need to do the following in your view:
>
> @Override
> public boolean dispatchTouchEvent(MotionEvent ev){
> return mGestureDetector.onTouchEvent(ev);
>
> }
>
> Thanks
> Rohit
>
> On Oct 31, 2:02 pm, Rohit Mordani <[EMAIL PROTECTED]> wrote:
>
> > I got fling/swipe to work. In one of my other posts someone told me to
> > do the following to make fling/swipe work
>
> > 1) Set View.setLongClickable to true for the view you are using
> > 2) Set GestureHandler.setIsLongpressEnabled to true
> > 3) Return true in your onDown method
>
> > Thanks
> > Rohit
>
> > On Oct 13, 4:55 pm, skink <[EMAIL PROTECTED]> wrote:
>
> > > On 13 Paź, 23:15, Rishi
>
> > > > I still don't understand why it acts differently for button. Either
> > > > way, what appears to have been happening is it does not reach to
> > > > ACTION_MOVE or ACTION_UP unless ACTION_DOWN is consumed by listener.
>
> > > it's not documented (i think) but in my opinion google designers treat
> > > down/move/up actions as a sequence of events. if you are not
> > > interested in down event the rest (move/up) won't appear.
>
> > > skink
>
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
