Hi Martin, thanks for your report. Can you please apply the patch attached to this ticket: http://trac.osgeo.org/openlayers/ticket/2987
More comments inline. On Jan 2, 2011, at 23:42 , Martin Saturka wrote: > Hello, > I tried the Bing layer, but it has two problems: > > 1) Some tiles are placed wrongly, they are around the right positions, > but still exchanged into wrong tile positions. The result is a funny > mosaics. In case you still see this issue after applying the above patch, can you please provide a minimal example showing this issue? If you can, please create a ticket for it. Otherwise use http://pastebin.com or a similar service. > 2) Putting the Bing layer into base layers causes event horrible > problems. When I click on a pop-up window, that pop-up window takes it > as a close event, and together with it puts a that clicking into the > map, even though close events are ended at the pop-up closing methods. > This mayhem only starts after some time (a few minutes) of map moving > and poi / pop-up clicking, thus it may be a reason why it was not > noticed. Are you sure that this only happens with the Bing layer? Anyway, can you also please provide a minimal example that shows the issue? Regards, Andreas. > As a result, the Bing layer is unusable now. > > M. > > On Sat, Dec 18, 2010 at 3:38 PM, Andreas Hocevar <[email protected]> wrote: >> 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. >> >> > > -- > Martin Saturka > Software Engineer, Sourcefabric > [email protected] > www.sourcefabric.org -- 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
