Hi, for those of you in need of commercial tiles, but not willing to bother with problems that come from the interaction between OpenLayers and external JavaScript APIs, the new OpenLayers.Layer.Bing with direct tile access may be a good option. Read more about it in this blog post: http://openlayers.org/blog/2010/12/18/bing-tiles-for-openlayers/
Regards, Andreas. On Dec 17, 2010, at 20:12 , Martin Saturka wrote: > Hello, > one possibility to deal with the "map data popups" at google v 3.3 is to > change the repositionMapElements method on OpenLayers.Layer.Google class - to > comment out two lines there: > //termsOfUse.style.display = ""; > //cache.termsOfUse = termsOfUse; > > This works well for me for both v3.2 and v3.3 of Google API. > > The v3.2 puts map data providers and terms of use link as a text, but it can > be wider than the actual map div. Then you will not see the whole string. > The v3.3 detects it, and when the data providers string is too large, it just > puts a link to the popup with the data providers. It is better then, since > you can see the strings appropriately. > > It looks that OL is confused by the change and supposes that the popup is > something to be shown (without clicking for it). > > M. > > -- > Martin Saturka > Software Engineer, Sourcefabric > [email protected] > > Subscribe to our Newsletter: > www.sourcefabric.org/newsletter/ > > Salvátorská 10 > 110 00 Praha 1, Czech Republic > http://www.sourcefabric.org > http://www.twitter.com/Sourcefabric > _______________________________________________ > Dev mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/openlayers-dev -- Andreas Hocevar OpenGeo - http://opengeo.org/ Expert service straight from the developers. _______________________________________________ Dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/openlayers-dev
