On Apr 5, 11:15 pm, patbenatar <[email protected]> wrote:
> Or would it be OK to use my already > existing, subclassed ItemizedOverlay to do this? I use an existing one; no need to use a separate Overlay. The performance hit in draw() is not noticeable > > > 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...] I am trying to say you are not necessarily receiving draw events as a result of all the interactions with a MapView. It may be sufficient however - I'd try this in the draw routine first, wiggle with it a little and see if this already get you there. If not, a more elaborate approach would be needed that "sweeps up" the remaining oddball cases which you didn't catch in draw(). Having said that, I figure your chances are good you can get this working through draw() alone. -- 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 To unsubscribe, reply using "remove me" as the subject.
