Hi, I should report the same thing.
My game Armaboing (www.armaboing.com) is multitouch since Android 1.5. And I have the same problem with multitouch, and came to think that it's not Android the problem but the drivers or the hardware. I think that's why Diane doen't want a bug report on this but I really hope it could be a glitch on the Android framework so that they can correct it. Maybe with a direct access to the sensors reading Android folks can tweak the data so that they are accurate before they get to us via the jvm ? I don't know if it can help but here's a few thing that I found to go around that bug : if you monitor both ACTION_UP and ACTION_DOWN on a single multitouch event "Up", most of the time one of the action returns the correct position for both points but one going down, the other going up. On my game which is made of very briefs tap on the screen, i count an Up And Down event as one and if the Down action didn't hit an object, then i check for the up event. Returns a few false positive but is much better than without the hack. I also noticed that if the two points are close on the X or Y coordinates, i have a lot fewer errors. Maybe you can adapt your controls to rely on that. One other thing I tried for another game(not released) is to get rid of the multitouch altogether. On the lower left corner i monitor the touchevent for direction and when i want to fire, i press harder (pressure and size event). Best regards. On 12 fév, 09:39, Kevin Duffey <[email protected]> wrote: > Ugh..sorry.. I hate using my moto droid to reply.. fat fingers and a > horrible physical keyboard don't go together. > > Dianne, I don't understand your response.. it's quite clear from several > developers that the multi-touch has problems severe enough that > it's deterring game developers and others that would use it. You're saying > that it's normal behavior for the multi-touch to change the location of 2 > touches such that one of them is completely not in the location of where you > touched it? Is this an Android platform issue with how it handles sensor > data.. or are you saying that the G1, myTouch, Nexus One and Moto Droid (not > sure about others) ALL have built their touch sensors to purposely report > this sort of behavior when you touch, then release, then touch again as > Robert and several other posters have state is happening? > > On Thu, Feb 11, 2010 at 7:46 PM, Dianne Hackborn <[email protected]>wrote: > > > > > On Thu, Feb 11, 2010 at 6:10 PM, Kevin Duffey <[email protected]> wrote: > > >> So what I want to know is what is being done about this? Is there a bug > >> file and if so is it > > > This is how the sensor hardware works. It is essentially the same sensor > > as the G1 and myTouch. Please don't file a bug about it. > > > -- > > Dianne Hackborn > > Android framework engineer > > [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. > > > -- > > 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]<android-developers%2Bunsubs > > [email protected]> > > For more options, visit this group at > >http://groups.google.com/group/android-developers?hl=en -- 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
