Dear List, I have more or less the same LayerSwitcher problem as described by Mike two months ago, but with Bing Maps.
I add BingStreetMap, BingAerialMap and BingHybridMap to my map. Then I try to click on the first one added in the LayerSwitcher. The radio button does only switch when I click the second time on it. And the Map does not appear! FireBug error: "mapInstance.GetCurrentMode() is null" Anybody any idea what the problem could be? Beate
---------------------------------------------------------------------------------------- Mike Leahy wrote: Hello List, I've noticed a minor issue when using Yahoo layers. This is currently visible if you open the spherical-mercator.html example (you may have to go with the development version athttp://openlayers.org/dev/examples/spherical- mercator.html, since the Google API in the 2.10 examples is not up to date). If you open the layer switcher on the map, then try switching through the Yahoo layers - you'll notice that switching to streets is fine, but the first time you click to one of the other two Yahoo layers, the layer switcher will not activate the radio input, so that it will appear that the previous active layer is still active, even though the map itself actually has been updated. The next time you click either one of these layers, it'll activate fine in the switcher. None of the other layers appear to be affected as far as I can tell. In addition to this, sometimes switching to these two Yahoo layers will cause error messages that seem to stem from the presence of Bing/VirtualEarth layers such as this one (copied from Firebug in Firefox): --------------------------------- v is undefined http://ecn.dev.virtualearth.net/mapcontrol/v6.3/js/atlascompat.js Line 401 --------------------------------- I cannot reliably reproduce this error, but if you try reloading the page and switching through often enough, it'll eventually happen. I have searched a bit, and far as I can tell no-one has raised this before, though it's not likely a show-stopper for anyone. Is this a known issue that I've missed, and/or is it worth reporting a bug? Regards, Mike _______________________________________________ Users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/openlayers-users
