> In fact, there isn't really a "primary" pointer.

Well, the documentation for ACTION_POINTER_DOWN says that this applies
to "non-primary pointers", which implies that there really *is* a
"primary" pointer.

So, I was just trying to explain why sometimes the pointers were
generating ACTION_DOWN, and other times were generating
ACTION_POINTER_DOWN, *in terms of whether the pointer is primary or
not, since this is how it is currently documented.*

But perhaps the easiest way to look at it is: If there's 1 finger
touching the device, expect ACTION_DOWN, ACTION_MOVE, ACTION_UP
events; but if there's 2 fingers touching the device, expect
ACTION_POINTER_DOWN and ACTION_POINTER_UP events.

(I'm assuming that there is never a situation where ACTION_UP and
ACTION_POINTER_UP are *both* generated for a single "finger up"
occurrence.  Please let me know if that's wrong, because I've never
actually tested this stuff, I'm just going by the limited Droid
examples posted by Dave.)

-- PJ



On Nov 16, 8:30 pm, Dianne Hackborn <hack...@android.com> wrote:
> On Sun, Nov 15, 2009 at 7:21 PM, niko20 <nikolatesl...@yahoo.com> wrote:
>
> > I wish though, that the multitouch would have also been natively
> > suuportedk in the sense that multiple views should get touch events
> > also simultaneously.
>
> Very, very deliberately not supported. :)  You'll need to look at the events
> arriving in a particular view and do what you want with them.  It is too big
> a can of worms to try to treat these as different event streams, because
> they really aren't independent, and in many cases the view of the first
> press really does want to see all of different finger touches during that
> motion.
>
> Also the data you get from the screen is likely not going to be completely
> independent with respect to multiple fingers -- for example on the
> G1/Sapphire class screen there are interactions between the two points
> reported, and if you play with Pointer Location on Droid you will see that
> pressing a second finger can cause noticeable jitter in the first finger.
>
> --
> Dianne Hackborn
> Android framework engineer
> hack...@android.com
>
> Note: please don't send private questions to me, as I don't have time to
> provide private support, and so won't reply to such e-mails.  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 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

Reply via email to