Thanks Andrew & Ozgur. I had an issue with anti-aliasing of one pixel wide strokes. I thought, incorrectly, the stroke could not spill over into the adjacent tile. Internet Explorer dithers the border pixels. The dithered pixels in the adjacent tile were being clipped causing ugly edges near the tile boundaries. It was a special case optimization for stroke weight=1. I have eliminated it.
I believe I have eliminated the extra white fill in the "Lake Michigan Shore" demo. The other demos appear to be working. The "Canada - Northwest Territories" case with 41,000 vertices produces a "script running slowly" message but it does eventually render the poly. Dragging, panning & zooming are very slow. I am trying to fix it. I will do the point reduction sooner in the assembly line. I will unroll the inner loop to process several pixels in the same iteration. If you find other demos not working properly, please let me know. Thanks again for your help, Berry -- 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.
