True, except the inconsistency results in an incompleteness. The onClick documentation doesn't state what mechanism has been created in the onClick case to produce the same effect as returning a false in the onTouch case.
On Nov 4, 11:10 am, Kumar Bibek <[email protected]> wrote: > Well, if the docs say it clearly, its fine I guess. > > On 04-Nov-2010 11:38 PM, "Bret Foreman" <[email protected]> wrote: > > It's unfortunate that onClick and onTouch do not use the same > approach, where the method returns a true if it handled the event and > the parent shouldn't get the event a false if the parent should get > the event. > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" ... -- 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
