If a map is configured with a permalink control and a center, the permalink control tries to work with the map center before setCenter is called. This sequence assumes that the map center will already be a LonLat. This fails if the map is constructed with a coordinate array. Safer move is to convert center to LonLat before controls are added.
When the list of event types became unconstrained in 501b42228a, we lost the documentation for events that are triggered. This change adds the list of events triggered to the API docs for events properties.
This allows us to simplify the map and layer configuration, because now the projection also defines defaults for maxExtent, maxResolution and units.
This change also adds transforms for SRS aliases for EPSG:4326 and centralizes axis order information in OpenLayers.Projection.defaults.
The new base layer may previously have been out of range, in which case setVisibility(true) would do nothing if the layer was visible already. So we check if it was previously out of range, and redraw it if necessary.
This change involves removal of the map's eventsDiv and introduces an OpenLayers.Events.buttonclick component that adds a buttonclick event which makes sure that only events that are not related to clicking a button propagate. This allows button controls to be on the map's viewPortDiv again.
'viewPortPx' parameter for OpenLayers.Layer.getLonLatFromViewPortPx
can be either a Pixel or a simple javascript object. 'lonlat'
parameter for OpenLayers.Layer.getViewPortPxFromLonLat can be either a
LonLat or a simple javascript object.
'px' parameter for OpenLayers.Map.getLonLatFromViewPortPx and
OpenLayers.Map.getLonLatFromPixel can be either a Pixel or a simple
javascript object.
The Map.html and WrapDateLine.html tests that check zoomToExtent were failing with the changes to this method. These test changes make the expectations more explicit. It is inconsistent to call wrapDateLine only in zoomToExtent, but this is the minimum change to get the tests passing again. It would be more consistent to call wrapDateLine in the setCenter sequence.
This is basically the same enhancement we made for intersectsBounds, and we no longer have to do dateline shifting in other components to get proper containsLonLat results.
