I even tried to open an infowindow with
map.openInfoWindowHtml(map.getCenter(), 'test'); map.closeInfoWindow();
That also did not fix the problem... :(
2008/9/9 Björn Brala <[EMAIL PROTECTED]>
> It's caused by the modularization of the *infowindow*. In v2.122 the
>> *infowindow* code was included in main.js but in v2.123 it has been moved
>>
>> to a separate module so that the API code becomes smaller on pages that
>> don't use the *infowindow*.
>>
>> The first time that you open the *infowindow*, the main API requests that
>>
>> the module be loaded, and pipelines any operations that affect the
>> *infowindow*. However, the API has no way to know that this code
>> for(i=0;i<this.NrTabs;i++) {
>> var Id='tab'+i;
>> document.getElementById(Id).className='tab';
>> }
>> refers to divs that are in the *infowindow*, so that code doesn't get
>> pipelined. It gets executed before the *infowindow* module code arrives,
>> and therefore before the div inside the *infowindow* gets created.
>>
>> The situation is similar to that which affected GOverviewMapControl in
>> v2.93. See: http://econym.googlepages.com/modularized.htm
>>
>> Try adding
>> TheMap.getInfoWindow().show();
>> just after you .setCenter() your map. GInfowindow.show() is implemented
>> inside the module, and therefore forces the module to be loaded without
>> actually displaying anything. Most other calls that don't display
>> anything, like map.closeInfoWIndow() and map.getInfoWindow() are
>> implemented in main.js and don't cause the module to be loaded.
>> --
>> http://econym.googlepages.com/index.htm
>> The Blackpool Community Church Javascript Team
>
>
> I've tried using this fix to force the infowindow script to load. The issue
> still stands. The map does not move to make the infowindow fit on screen.
>
> 2008/9/9 Rossko <[EMAIL PROTECTED]>
>
>
>> I haven't looked in detail to see if this is your issue, but since API
>> version 122 the infowindow code has been modularised and can cause
>> first-time funnies.
>>
>> See -
>>
>> http://groups.google.com/group/Google-Maps-API/browse_thread/thread/424ad972c82e490b/3b3ada6b259d0c5c?lnk=gst&q=infowindow+williams#3b3ada6b259d0c5c
>> which is a different funny, but it's worth trying the fixes. Either
>> regress to v2.122 or earlier, or try Mike's circumvention.
>>
>> cheers, Ross K
>>
>> >>
>>
>
>
> --
> Bjorn Brala
> ----------------
> Google maps - Swis Webdesign
>
--
Bjorn Brala
----------------
Google maps - Swis Webdesign
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
