Since v2.169 or perhaps earlier, problems with GGeoXml when kml file is large (>100kb)
This turns force_mapsdt = true which means it forces GGeoXml server to generate the kml tiles instead of client-side shape rendering. This creates multiple layers for one kml file and causes issues for geoxml.hide() and removeOverlay(geoxml). The implementation (or hack) in these versions: geoxml.show() is actually addOverlay(geoxml) - causing problem with removeOverlay(geoxml) and addOverlay(geoxml) subsequently. When force_mapsdt = true, not only it creates an instance of GTileLayerOverlay, it also creates instances of shape GOverlay for all the shape elements in the kml and added to the map (I believe this is not necessary since the shapes are not drawn client-side). This implementation causes the Issue 1234: "GGeoXml.hide() does not disable mouse events" and makes geoxml management a bit harder. http://code.google.com/p/gmaps-api-issues/issues/detail?id=1234&q=GGeoXml&colspec=ID Briefly for a day or 2 back in July 9-10, this was fixed by removing the extra unnecessary shape overlays, and GGeoXml methods were behaving properly. For some unknown reason Google reverted back to the buggy unmanageable implementation todate. These issues cause excruciating headache when your map app provides dynamic layer UI for large kml files. The observation above were substantiated with the addOverlay event callback and with the help of Firebug. You can also test some of these phenomena by playing with the simple example below. http://www.genes.com/maps/geoxml_test.htm On Aug 6, 5:25 pm, "Dann (Google Employee)" <[email protected]> wrote: > Hey everyone! > > We've recently pushed v2.170 as v2.x and upgraded v2.164 as v2. No > issues were resolved or changed in this release. > > As always, please discuss anything in this forum (http:// > groups.google.com/group/Google-Maps-API/) if you think there is a > regression, and report it in the issue tracker (http://code.google.com/ > p/gmaps-api-issues/issues/list) if others confirm your suspicions. > > Today, we released 2.160 as v2.x and 2.159 as v2. > > The full changelog is available > here:http://code.google.com/p/gmaps-api-issues/wiki/JavascriptMapsAPIChang... > (If the groups interface cuts the link off, you can find it in the > wiki tab of the issue tracker). > > As always, please discuss anything in the forum (http:// > groups.google.com/group/Google-Maps-API/) that you think may be a > regression and report it in the issue tracker if others confirm your > suspicions. > > Thanks! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" 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-Maps-API?hl=en -~----------~----~----~----~------~----~------~--~---
