the page works for me. the upshot is that MotionEvent.toString() includes dumps of x2 and y2 which are the last coordinates of the second touch point. slight complication is that they are not reset on a single touch event so a client would have to track them and detect a new multitouch event when they change.
this comes as a big surprise to me! the other multitouch hack overloads MotionEvent.getSize() to include dx/dy information for a second touch if there is one. this is all well and good, but the diffs *add* multitouch code to the kernel, implying there wasn't any to begin with. if this toString() hack works on a release kernel, then there are other places that touch is being processed, or there are different kernel forks... i hope that in the face of multiple hacks, the multitouch thing is just officially implemented ASAP! >That webpage doesn't appear to exist. > > >On Mon, Aug 17, 2009 at 11:41 AM, Hekki<[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 >> >> Hope that helps >> >> Yahel >> >> On 29 juil, 19:35, Marco Nelissen <[email protected]> wrote: >>> This was discussed a few days ago. Search the archive. >>> >>> On Wed, Jul 29, 2009 at 4:33 AM, Anastasiya >>><[email protected]>wrote: >>> >>> >>> >>> > Hi. >>> > Does Donut really support multi-touch? If yes, where I can find this >>> > support in code? >>> >>> > Thanks. >> > >> > > -- 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 -~----------~----~----~----~------~----~------~--~---
