Well Android started without any multi-touch API at all, a simple version was added in an update (with the constraint that the platform itself couldn't use it for anything), and it has been evolving since then. I certainly agree that the initial API was difficult to use for some common things, because it was just a low-level API to provide the information for apps but apps had to manually deal with the data themselves. I don't know why you think the implementation was poor, though I would actually say the general touch event implementation was less efficient than it could be (due to schedule needs for shipping a product), and the current implementation that first appeared in 2.3 is much better.
One bit of advice: you may want to stop and think about calling people morons for things when you don't actually know the reasons and design trade-offs that were involved in the decisions. On Wed, Nov 30, 2011 at 1:47 PM, niko20 <nikolatesl...@yahoo.com> wrote: > Dianne I appreciate your help in the forums and your hard work on > Android. However, I think you even have to admit that multitouch, at > least in its original form, is a poorly implemented, complicated API. > If they cleaned it up as of Android 3.0, that is good news for devs. > > -niko > > On Nov 30, 2:45 pm, Dianne Hackborn <hack...@android.com> wrote: > > On Mon, Nov 28, 2011 at 6:21 AM, niko20 <nikolatesl...@yahoo.com> wrote: > > > I guess in Android 3.2 they now allow multitouch to go the multiple > > > views. But I have not tested it. > > > > This was added in Android 3.0, and it does work. > > > > > Whoever thought of the one view thing is a moron, period. It should > > > have just worked. But noooooo. We are Google we do everything the hard > > > way. > > > > Well I guess I can live with being called a moron. What shall I call > you? > > > > -- > > Dianne Hackborn > > Android framework engineer > > hack...@android.com > > > > 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 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 > -- Dianne Hackborn Android framework engineer hack...@android.com 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 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
