On 6/25/2010 9:48 AM, Pil wrote:
If this is the case I would say it's a clear bug.
> So it seems there's nothing more you can do at the moment except to
> report a bug and hope that it'll be fixed soon.
Darn, I was hoping it was just me! I have reported both of these issues
as bug 2526:
http://code.google.com/p/gmaps-api-issues/issues/detail?id=2526
I left them a simplified test case so I can continue with (as per
Damsel's suggestion) ditching KmlLayer and writing my own
Marker-insertion code.
Thanks for your interest, guys. If the bug makes progress I'll update
the thread, for the sake of those who encounter it later.
--
HostGIS, Open Source solutions for the global GIS community
Greg Allensworth - SysAdmin, Programmer, GIS Person, Security
Network+ Server+ A+ Security+ Linux+
PHP PostgreSQL MySQL DHTML/JavaScript/AJAX
"No one cares if you can back up — only if you can recover."
--
You received this message because you are subscribed to the Google Groups "Google
Maps JavaScript API v3" 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-js-api-v3?hl=en.
