With a simple hack in place, the API GLayer attempts to load YouTube layer tiles that look like this:
http://mlt3.google.com/mapslt?lyrs=lmc:youtube&x=2013&y=1318&z=12&w=256&h =256&source=maps_api The lyrs server sees the &source=maps_api and returns a single invisible pixel instead of the image you'd expect from http://mlt3.google.com/mapslt?lyrs=lmc:youtube&x=2013&y=1318&z=12&w=256&h =256 The code that adds the &source=maps_api is hard coded into the external mod_lyrs.js module http://maps.google.com/intl/en_ALL/mapfiles/141e/maps2.api/mod_lyrs.js and looks like this: v.source="maps_api"; So a dirty hack would have to load a hacked version of that external module, not easy, and even then it might not handle the hotspots. You could write your own GTileLayerOverlay that used the &source-less tiles, but it certainly wouldn't run the YouTube videos. There can't possibly be a clean release of a YouTube GLayer until at least v2.143, since the mod_lyrs.js module would need new code to recognise the new layer id and generate the "lmc:youtube" part of the tile request. Such code is not present in the v2.142 version of the module, which is hardcoded to only translate the panoramio and wikipedia layer ids. -- http://econym.org.uk/gmap The Blackpool Community Church Javascript Team --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
