i'm not planning on including *any* multitouch support in a shipping product. part of my job is developing gesture algorithms and writing demonstration applications, for which i control the environment - therefore a hacked kernel or even toString() is OK.
at the moment, all i have is the distance-magnitude hack, which mostly works but isn't great as you imagine. i hear all kinds of rumours about vendor-specific multitouch, most of which i can't repeat. it would be great if the issue was sorted before people have to start writing vendor-specific code. (note that the HTC Hero already has multitouch, but zoom only, which maybe means it's built on the distance hack.) thanks, j >I can't see the page that was posted, but the base framework doesn't >print any second touch information in a MotionEvent, there is no >such information there at all. This person is probably running on >someone's device that has modified the based framework and happens >to print this information. Anything one does based on that is >likely to only work on that vendor's flavor of the platform. > >(And seriously, relying on the output of toString()? You are >setting yourself up to break in the future.) > >On Mon, Aug 17, 2009 at 12:44 PM, Jason Proctor ><<mailto:[email protected]>[email protected]> >wrote: > > >update: i'm not seeing the x2 and y2 coordinates in event.toString(), >at least on a release cupcake kernel. maybe the guy was using an >older kernel, with residual code following the (presumed) removal of >the multitouch stuff? > >(and this now gels with the other multitouch hack, which is a relief >of sorts...) > > > > >>I wonder if x2 and y2 of MotionEvent could be fetched by means of >>reflection, using setAccessable() and then uptain their values. A >>SecurityManager might get in the way though?! >> >>/Casper >> >>On 17 Aug., 21:09, Marco Nelissen >><<mailto:[email protected]>[email protected]> wrote: >>> That webpage doesn't appear to exist. >>> >>> On Mon, Aug 17, 2009 at 11:41 AM, >>>Hekki<<mailto:[email protected]>[email protected]> wrote: >>> >>> > Hi, >>> >>> > I've turned quite a lot to find info and how to for multitouch, so i >>> > finally made my own. The answer is : >>> >>> > Multitouch is already usable in Android SDK : >>> >>> >>> ><http://www.alicesbiscuit.com/android-sdk-multitouch-workaround.html>http://www.alicesbiscuit.com/android-sdk-multitouch-workaround.html >>> >>> > Hope that helps >>> >>> > Yahel >>> >>> > On 29 juil, 19:35, Marco Nelissen >>><<mailto:[email protected]>[email protected]> wrote: >>> >> This was discussed a few days ago. Search the archive. >>> >>> >> On Wed, Jul 29, 2009 at 4:33 AM, Anastasiya >>><<mailto:[email protected]>[email protected]>wrote: >>> >>> >> > Hi. >>> >> > Does Donut really support multi-touch? If yes, where I can find this >>> >> > support in code? >>> >>> >> > Thanks. >> > >-- > >jason.software.particle > > > > > > >-- >Dianne Hackborn >Android framework engineer ><mailto:[email protected]>[email protected] > >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. > > > -- jason.software.particle --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
