After the announcement of 2.12-rc3 on this list, I tried that and unfortunately the same problem shows up on there as well. The reason I wanted to switch to 2.11 in the first place was the fact that the measurement on Control.Measure could be displayed immediately and not only on finishing a line, but for now, when this app is moved to production I will have to stick to 2.10 until I can find a solution.
I was thinking that maybe I would disallow selection of the centerline layer until the user is at a specific zoom level, and once they zoom out too far, switch over to the routes layer, and when they leave the zoom level for that one, turn both off. With that solution the browser shouldn't suffocate on the large amount of data anymore, even though it would probably still reload the data at that time when I call setVisibility(false) on the layer. -- View this message in context: http://osgeo-org.1560.n6.nabble.com/OpenLayers-2-11-loading-layer-data-regardless-of-maxResolution-tp4950549p4958101.html Sent from the OpenLayers Dev mailing list archive at Nabble.com. _______________________________________________ Dev mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/openlayers-dev
