Testing on my xperia play shows that it goes up to Pointer ID 15 and then starts over again! Why 15? No clue...
This is inconsistent behavior when compared to all other multitouch Android devices. I'm going to end up implementing the same remapping solution for all my multitouch games and frameworks. On May 17, 5:51 am, Mario Zechner <badlogicga...@gmail.com> wrote: > So, i wondered why we had that assumption. Back in 2009/early 2010 > when 2.0 came out and the Droid blew away the world this group was > full of multi-touch related topics. Dianne Hackborn answered ALL our > questions back then, a feat that probably took up all her work > time :P. She also explained how pointer ids are handed out by the > system. > > original > message:http://groups.google.com/group/android-developers/msg/2786021d43ae196d > > quote: "If finger A goes down, then finger B, then finger A > is released, you will see pointer #0 going up and the following > movements > will have only pointer ID #1 (at index 0 because that is the only > active > pointer). When the next finger goes down, it is given the first > available > pointer ID (there is no way to know "which" finger this is, so we > assume the > first available), thus you see a new pointer ID 0 going down." > > So, the first available pointer id is chosen. That was our assumption > as well. There are a few more threads on the group that go into > pointer ids and how they are generated. > > It seems theXperiabreaks this assumption. Would be nice to hear an > official word on this. > > On 17 Mai, 04:25, Michael Leahy <mleahy....@gmail.com> wrote: > > > > > > > > > >"It looks indeed as if Sony was brewing their own special kind of > > > 'fragmentation'" > > > I've come to a succinct definition of "fragmentation" at least from a > > developer perspective as unfortunately this term is widely "misused and > > abused" in the press and sometimes twisted in definition by organizations > > that produce it. > > > "Fragmentation is what happens when OS and device differentiation fails to > > honor standards and contracts of developer APIs." > > > This covers faults in various OS versions and various ODM faults as well at > > least from a developer perspective. OS / device differentiation should be > > celebrated; fragmentation as defined above... not so much. > > > --Mike > > > On Mon, May 16, 2011 at 7:08 PM, Mario Zechner > > <badlogicga...@gmail.com>wrote: > > > > I don't have direct physical access to anXperiamyself so i can't > > > comment on the button issues Robert discovered. It looks indeed as if > > > Sony was brewing their own special kind of "fragmentation". -- 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
