Hey Phil, this sounds reasonable. Would you be able to create a patch or issue a pull request?
Thanks, Andreas. On Tue, Feb 7, 2012 at 1:35 AM, Phil Scadden <[email protected]> wrote: > And yet further to this... I dont think > > return withinMaxExtent || this.layer.displayOutsideMaxExtent || > this.layer.wrapDateLine; > > is actually needed at all. Just leave as > return withinMaxExtent || this.layer.displayOutsideMaxExtent; > > The code for > this.bounds.intersectsBounds(maxExtent, {inclusive: false, worldBounds: > worldBounds})) > seems to deal with the wrapDateLine issue adequately. > > So in summary, I am just proposing that the lines > > if (this.wrapDateLine) { > this.displayOutsideMaxExtent = true; > } > > in Layer.js be removed as redundant. This would allow restricting a > layer to maxExtent even it crosses the dateline. > > > Notice: This email and any attachments are confidential. If received in error > please destroy and immediately notify us. Do not copy or disclose the > contents. > > _______________________________________________ > 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
