Hi, On Nov 24, 2010, at 13:25 , Fernando Barbat wrote:
> I followed this example > http://dev.openlayers.org/releases/OpenLayers-2.10/examples/google-v3.html, > but I couldn't move the attribution divs. It looks like somebody is setting > the position properties directly to the element every time I pan or zoom. > This way, the CSS properties I declared in the CSS files get overwritten. "Someone" in this case is the GMaps API itself. We register events to take these divs and move them to the top of the layer stack, so the Google icon and the Terms of Use links are clickable. But you should be able to customize .olLayerGoogleCopyright and .olLayerGooglePoweredBy without any problems. > It is strange too that the classes which are asigned to these elements are > both in google.css and style.css. This is for historic reasons. google.css makes sure that these divs end up in the original positions of the GMaps API. If you don't include google.css, they are positioned differently to play well together with the OpenLayer Attribution control. > Finally, I noticed that this problem doesn't happen with OpenLayers and > Google Maps v2. The v2 API was less aggressive in modifying the attribution divs, but the approach is the same. > Any idea? Maybe you tried to set style properties programmatically on the divs, instead of using css classes? Regards, Andreas. > > Thanks. > > Fernando > > _______________________________________________ > Users mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/openlayers-users -- Andreas Hocevar OpenGeo - http://opengeo.org/ Expert service straight from the developers. _______________________________________________ Users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/openlayers-users
