On Mon, Nov 1, 2010 at 2:51 PM, Mike Reed <[email protected]> wrote:
> I didn't realize that onTouchEvent() was responsible for calling all the > overlays onTap()s. > Neither did I until I saw your post. Then I put a break point in my overlay's onTap method and looked at the stack trace. Without the source code or decent documentation, this a cheap way to get a better idea of how the maps API works. Every little bit of knowledge helps when you're forced to work around it's many shortcomings :-) ------------------------------------------------------------------------------------------------- TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago transit tracking app for Android-powered devices -- 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
