I have come across a last minute bug/performance issue in IE when adding Polylines with addOverlay. Due to the requirement of the solution, I need to cut up a polyline once it comes back from the Directions object. Cutting up is fine, I get the Routes, get the PolyIndex and step through the LatLngs of each step and create a new Polyline of each segment.
The problem occurs under IE when I try and add the Overlay, it takes x10 as long as FF/Chrome to render the Polyline segments to the Map. I have been trying to optimise my Javascript all day as I thought that may be the issue, but I came across the SVG data in Firefox and saw a lot of duplicate data, eg. Maps was duplicating the same SVG point multiple times (10 - 20 times in fact). Any chance under IE that the VML code would be the same, duplicate points which aren't required which would cause the performance hit when trying to render the polyline? I know one of the rules is I need to post code, but I am painted into a corner here as I am unable to. I am more looking for feedback as I am trying to rule this out and therefore allowing me to concentrate optimizing a couple of the more intense methods. Is there anyway to simplify the poly (Points/Pixels not LatLng) using the current Projection some how? Regards, Mark -- 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.
