JP- Thanks for your feedback! It has been very enlightening. Overriding draw() sounds like a great idea that would cover any possible form of interaction with the Map.
Just to make sure I'm clear on the basic idea here: you're saying create an additional, empty MapOverlay, and purely using that Overlay to track motion on the map? Or would it be OK to use my already existing, subclassed ItemizedOverlay to do this? > There's a residual chance that you don't receive that final .draw() to > trigger the call for data when it would be warranted. A Thread that > checks for such cases at, say, 200ms intervals, could be used to pick > up such cases. Or, use that Thread exclusively to monitor the speed at > which the map moves. I don't understand... Why would I not receive the final draw() call? Doesn't the Map HAVE to draw itself? If I don't receive the final draw() call, that means the Map wouldn't be getting drawn at that final point where the Map comes to a rest [correct? If I'm subclassing the Overlay and the Overlay needs to draw itself to ensure all its items are visible--this would be proper behavior--if I don't get the final draw, no one does.... that doesn't make sense...] Kinda a pain in the ass that we have to be so hacky to achieve such key functionality! Thanks so much! Nick -- 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 To unsubscribe, reply using "remove me" as the subject.
