On Jan 20, 7:33 am, Andrew Leach <[email protected]> wrote: > On 20 January 2011 15:22, [email protected] <[email protected]> wrote: > > > Particularly since v2 is deprecated and isn't supposed to be changing. > > But KML rendering has changed: there have been issues reported > elsewhere where complex KML has upset the renderer. That may have been > Version 3, I can't remember; but a server-side renderer may well be > shared between the client-side APIs anyway.
I think it was with KmlLayer in v3. Regardless, if this issue is with GGeoXml and it has changed recently (which the OP indicated), it is an issue for v2 and should be fixed, preferably before they stop work on v2 entirely... If it is an issue in v3 then it should be raised there as well (it is probably a problem on google maps itself as well, I think they all share the same KML engine). -- Larry > > dersmich, > > If you use GGeoXml, then how that appears is outside your control. If > you want control, you need to plot the polygons yourself. With complex > polys, you will run into problems because of browser capability. > > Raising an issue can't do any harm; but Google don't look at the > Version 2 issues list very often. And they may well say that GGeoXml > is a black box as far as the browser is concerned. You get what you > get. -- You received this message because you are subscribed to the Google Groups "Google Maps API V2" 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.
