Thanks. I hadn't thought of using a Polygon to capture past maps bounds. I think the idea has merit, but I use a SQL query on the server side to get new locations for the Overlay Manager. I do something like "where lat/lng in ( current bounds ) and lat/lng not in ( old bounds #1 ) and lat/lng not in ( old bounds #2 ) ..." (psuedo code obviously).
I'm not sure how I would efficiently communicate the union'd polygon to the database. I know MySQL has spatial capabilities, but I've never used them. If I could send the polygon's vertices to MySQL and have it do all the processing, that'd really be great. It turns out that the way people view maps, the BoundsCachingListener is really efficient in regards to storing the past map bounds. Because people tend to find a location, then zoom out, and then back in on another location, when they zoom out, the past map bounds that are entirely contained within the new map bounds are removed from the cache. I welcome any help on this, Eric --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" 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/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
