@Jeffery. Thanks for the updated info. I definitely second Mario's suggestions of writing a clear and informative post on the dev blog and update MotionEvent documentation to state the things you did here. Otherwise the contract is a bit of a mystery and there is no way for us to know about changes either if it's not documented all the way. I too was handling it by "first free pointer id is returned" kind of way based on implementation tips and discussion on this list when the API first appeared.
On May 17, 4:29 pm, Mario Zechner <[email protected]> wrote: > I'd strongly suggest to either write a new dev blog entry on multi- > touch that clearly states all your points in your post or updating the > MotionEvent documentation which is still very ambiguous. -- 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
