I had a look at Lukes "hack". Very clever, smart guy! Except when I ran the multi-touch visualizer on my G1 it never actually showed me multi-touching (he did explain in his blog that the G1 hardware didn't support multi-touch very well).
It would be really easy to implement a multi-touch SDK interface, they could do any of these: - Double the size of the float[] returned on onSensorChanged - Return a different sensor number for each touch - Add a new interface method. :) Anyway, my multi-touch plans have been shelved until I hear more news. Thanks to all for replying. Cheers. On Jul 2, 10:37 pm, Disconnect <[email protected]> wrote: > On Wed, Jul 1, 2009 at 8:10 PM, CraigsRace<[email protected]> wrote: > > > Back on topic, and I'll make it a multiple choice question (in a hope > > it will get answered). > > > Does anyone know if the Android SDK will support multi-touch: > > A) In the next month > > B) In the next 6 months > > C) In the next year > > D) Multi-touch is still being discussed > > E) Multi-touch will not be supported for the foreseeable future > > F) Not allowed to talk about multi-touch > > ? > > Last time it came up (when Luke did his psuedotouch hack) the answer > was - patents/etc aside - mostly a mix of D and E. Specifically, > they'd love to see proposals and ideas for SDK support (including > clean/reasonable fallback for single touch, the psuedotouch G1 does > and proper multiple-simul-locations multitouch) and would prolly help, > a little, with the implementation. > > So .. G) We'd love to hear actual proposals but its OSS so "do it yourself" --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
