If the move event had the pointer index encoded in it, then we would need to deliver separate events for each pointer, which is a lot less efficient and I think ultimately a lot harder to deal with (vs. having all of the data available in one event).
Anyway, this is really not an issue. Please read Andy McFadden's blog post on using newer API while being compatible with older platforms. You'll probably want to follow the latter part, where you have a separate class in your app that calls the new APIs and you make sure to not try to use on older platforms. http://android-developers.blogspot.com/2009/04/backward-compatibility-for-android.html <http://android-developers.blogspot.com/2009/04/backward-compatibility-for-android.html> On Sat, Dec 26, 2009 at 11:49 AM, rageman <nene...@gmail.com> wrote: > Trying once more, all replies seems to end up in the void :-( > > Unfortunately the design of the multi touch api requires new api calls > introduced in 2.0. > In my opinion it would be nicer to have added a index for the move > event in the same way as on the up/down event. > This would have leave the api fully backwards compatible. > > We would like to support platform 1.5 - 2.x with the same SKU and > support multi-touch on the 2.x devices and single touch on the other. > Is this still possible when using function calls introduced in 2.0? > In C/C++ even objective C you could use weak pointers, is this also > possible in Java on Android? > > Any help would be very appreciated :-). > > Cheers, > > On Dec 26, 7:33 pm, Dianne Hackborn <hack...@android.com> wrote: > > There is currently no official sample code, but you can look at the > > PointerLocation (from Dev Tools) code: > > > > http://android.git.kernel.org/?p=platform/development.git;a=blob;f=ap... > > > > On Thu, Dec 24, 2009 at 10:30 PM, pcm2a <reeeye...@gmail.com> wrote: > > > Are there any multitouch code examples that Google provides for SDK > > > levels 2.0 or higher? I do searches on here and on google and come up > > > empty. > > > > > -- > > > 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<android-developers%2bunsubscr...@googlegroups.com> > <android-developers%2bunsubsÂcr...@googlegroups.com> > > > For more options, visit this group at > > >http://groups.google.com/group/android-developers?hl=en > > > > -- > > 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<android-developers%2bunsubscr...@googlegroups.com> > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- 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
