This gives users control over where a callout should join to the label
text. (Previously, you only had control over where the callout would
join to the corresponding feature geometry).
Choices include:
- Closest point (previous behavior)
- Label Centroid
- Fixed corners: Top left/top right/bottom left/bottom right/etc
Data defined control over the label anchor is also possible
* MDAL 0.5.90 : support for custom Logger and 1D meshes
* [FEATURE] [MESH] Support rendering of 1D meshes, see https://github.com/qgis/QGIS-Enhancement-Proposals/issues/164
1D mesh consist of edges (edge is straight line segment with 2 vertices) and the data that is defined on either
vertices or edges. Such data can be loaded by MDAL and rendered as mesh layer in QGIS.
Adds:
@map_start_time: Start of the map's temporal time range (as a datetime value)
@map_end_time: End of the map's temporal time range (as a datetime value)
@map_interval: Duration of the map's temporal time range (as an interval value)
When designing a model, users typically will need to run the model
many times as they tweak its structure.
This change causes the parameters used when running the model from
the designer to be remembered and saved into the model, so that
each time you run the model from the designer you don't have to
re-set all the input parameter values to the desired test ones.
Makes iterative model design SO much easier!
Sponsored by Alta Ehf
cached images we have of temporal enabled layers
Otherwise these will not be re-rendered using the update temporal range
when the canvas is redrawn (and we want to avoid a full map redraw during
animations, which is expensive, so we want to be able to reuse as many
cached images as possible!)
The QgsTemporalProperty interface has members which are geared more to
user-setable temporal properties (e.g. "isActive()"/"setIsActive()". Instead, use
more explicit "hasTemporalCapabilities()" API in
QgsDataProviderTemporalCapabilities to make it immediately clear
what this flag means for data provider temporal capabilities
