What happened was that the infowindow code got moved out of the main API code and into an external module in v2.123. Since then, the first call that you make to a method that's implemented in that module gets pipelined and the infowindow code module gets fetched asynchronously.
When you call new GFslideShow(samples, "slideshow", options); and new GFslideShow(snaps, "mouldshow", options); the first time, the module won't have been loaded, so the "slideshow" and "mouldshow" divs take a while to be created. There's no callback on a module load, so you can't know when it's safe to reference something that's going to be inside the infowindow contents. What you can do is perform map.getInfoWindow().show(); as soon as you create the map, and hope that the module gets loaded before you need it. Since there is no hidden infowindow, the .show() doesn't do anything at that point, but calling it does force the module to be loaded. -- 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 -~----------~----~----~----~------~----~------~--~---
