Jean, Cameron is right that the behaviour you are encountering is a new "feature".
Jean Pommier (IGE) wrote: > Nevertheless, there's still an issue : by setting the OWSContext > Bounding box, i'm fixing a limit to the areas the users can go to : i > can't zoom on an area out of this bounding box (even if, of course, at > large scales, we can see the parts of the map outside of the boudngin > box). Is it clear ? You are right. This is because we set a limited maxExtent. This concept is in MapBuilder since the initial version of MapPaneOL. And although nobody has yet complained about it, I still consider it an issue. > I suppose the clean way in my case would be not to set the OWSContext > Bounding Box to such a limited area, but, let's say to (-180, -90 > 180,90), and to set the MapPaneOL's center and initial Zoom, but i > find no tag for that, in MapPaneOL. So what's up ? Is it not possible > at the moment ? Is it elsewhere ? The correct way to do it would be to use Proj4js to get (-180,-90 180 90) projected to the map SRS and set that as maxExtent of the map. After loading the layers, map.zoomToExtent would have to be used to set the map to the extent specified as BoundingBox in the context. However, this behaviour should be configurable, in order to not break WMS-T layers that do not provide tiles for the whole planet. If you are successful in setting this up, we would be glad to have it as contribution and use it as fix for the upcoming 1.5rc2 release. Regards, Andreas. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Mapbuilder-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mapbuilder-users
