While optimizing code I found that, somehow inherently, a single call to com.google.android.maps.MapView.postInvalidate() triggers two calls to com.google.android.maps.onDraw(), within a single event cycle. This of course noticeable slows down Overlays that display a lot of elements on a MapView, as any additional calls to onDraw() within a single event cycle are redundant. I was able to trace the problem back to com.google.android.maps.OverlayBundle, which calls com.google.android.maps.Overlay.draw() from lines 42 and 45... This is Donut 1.6 but I know this was the case in earlier releases of Android as well. I tried to rearrange and disable a few things in my app (such as the display of zoom controls), but could not isolate the condition that triggers these redundant calls. I wasn't able to track down OverlayBundle.java either, to see what's in that particular area of the code.... so my question is whether anybody seen this effect as well/or is able to provide a few pointers?
--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
