The automatic resolutions work unreliably (mostly due to geometry precision) and
therefore cannot be use reliably. Therefore they should rather be treated as a
technology preview which can be opted into for the moment.
This algorithm creates a polygon layer containing the extent
of a print layout map item, with attributes specifying the map
size (in layout units), scale and rotatation.
The main use case is when you want to create an advanced overview
indicator and the inbuilt layout tools to do this don't suffice.
are displayed
Turns out there is NO reliable way to create a proxy model
which adds new rows to a model, so just bite the bullet and
do it in the underlying model (yuck)
[feature] [mesh] #20731 add option to format time in mesh layer
There is new settings dialog that can be opened by button next to time slider. User can set reference time and time format (e.g. 2019-03-21 22:01:11).
Single geomtry checks (is valid) are exuted on the fly, if the map canvas suddenly
changes the current extent while fixing a geometry this becomes very nervous for
a user.
When init()ing QgsDualView through the attribute table it is
usually done BEFORE the model has been populated, so this code
has no effect and throws a warning.
There's no feature regression by removing this - the first
entry is still selected by default (elsewhere)
This adds a new parameter type specifically for map scales,
QgsProcessingParameterScale. The values are evaluated using
self.parameterAsDouble, which returns the map scale
denominator (matching the standard in other parts of the
QGIS API).
Scale parameters are displayed to users using the standard
QgsScaleWidget, which includes the combo box of predefined
scales and a shortcut button to match the current map scale.
when a layer with unknown CRS is loaded in a background thread
We can't queue the connection to prompt for CRS (or warn via
messagebar), because the slot uses a modifiable reference which
may be deleted before the queued slot is called.
We also can't do ANY gui related stuff when this occurs. Best
we can do is log a warning and move on...
