There is a new check box that allows the user to tell whether a map should
keep the layer styles (it will store the state when the check box is checked).
The stored layer styles keep a snapshot of each layer's configuration
instead of just keeping name of the style.
This solves issues with styles and visibility presets in composer which were
not completely compatible.
This code has been funded by Tuscany Region (Italy) - SITA (CIG: 6002233F59)
and commissioned to Gis3W s.a.s.
- style manager is always enabled (client code does not need to distinguish between enabled/disabled state)
- layers currently active style is stored only in QgsMapLayer - in style manager it has entry with no data (avoids duplication of data)
This also solves issues with visibility presets and styles when some presets do not have stored style
[FEATURE] Support for multiple styles per map layer
Available in legend context menu in Styles sub-menu where it is possible to add/remove styles
and quickly switch between them.
In version 2.6, new keywords has been added to Expression :
* $currentfeature - returns the current feature
* $atlasfeature - returns the atlas feature
* getFeature - gets a matching feature from a layer
But I think, Expression lacks a few keywords :
* geometry - returns the feature's geometry
* transform - returns the transformed geometry
These new keywords can be used with getFeature for some geometry tests like
intersects, crosses, contains, etc
Tests has been added to geometry and transform in Expression
See http://hub.qgis.org/issues/11814
NOTE: the map rotation should likely be considered at LabelPlacement
configuration rather than at rendering time
Raises pixel mismatch tolerance for background labels tests
Includes widget to show and set map rotation.
Handle rotation in vector and raster renderers.
Ensure correct behavior of panning and zooming actions.
Drop compile-time defines for ARM and ANDROID, leaving only
the qreal based function to transform in place.
Update expected test results after eye comparison.
This is much faster way of initializing a spatial index. From python it is as simple as
>>> index = QgsSpatialIndex( layer.getFeatures() )
From a simple test with 50K points in a memory layer:
- bulk loading ~ 100 ms
- inserting features ~ 600 ms
The index tree should be in theory also better constructed and may result in faster lookups.
