It would seem logical for the .openInfoWindowTabs call to move the node
into the info window rather than take a copy, that's what the non-Html
version of .openInfoWindow does.
The workround for .openInfoWindow is to .cloneNode() the data.
The workround for .openInfoWindowTabs would be to clone the Tabs. That
is possible, but only by using the undocumented properties (name and
contentElem) of GInfoWindowTab.
I don't understand the purpose of your "m" marker, so I've not bothered
using it in this code:
GEvent.addListener(map, "infowindowopen", function() {
var iw = map.getInfoWindow();
var tabs = iw.getTabs();
var tabs2 = []
for (var i=0; i<tabs.length; i++) {
tabs2.push(new GInfoWindowTab(tabs[i].name,
tabs[i].contentElem.cloneNode(true)));
}
map2.openInfoWindowTabs(iw.getPoint(), tabs2,
{pixeloffset:iw.getPixelOffset()});
});
The code gets the tabs from the infowindow, then creates a new tabs2
array, copying the "name" and cloneNode()ing the "contentElem" of each
of the tabs. The (true) parameter of .cloneNode causes it to copy all
the child elements of the node.
Because this relies on undocumented properties of GInfoWindowTab, you
should specify a specific version of the API (e.g. v2.156) that's known
to support those properties.
--
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
-~----------~----~----~----~------~----~------~--~---
