The python test test_qgsrelation.py was failing for misterious reasons
(the very same test was passing if run from QGIS application), I tracked
the issue down to the addition of QgsOptionalExpression mCollapsedExpression;
in QgsAttributeEditorContainer.
The new c++ test replicates the python test and make sure there are no
problems with the change style operation.
Allows elevation properties to be set for vector layers, including:
- altitude binding
- altitude clamping
- extrusion
- scale
- offset
These properties can be set through the new "Elevation" tab in
the vector layer properties dialog
Allows elevation properties to be set for raster layers, including:
- whether raster values represent heights
- scale
- offset
These properties can be set through the new "Elevation" tab in
the raster layer properties dialog
also update the internal name of that parameter and all child algorithms
in the model accordingly
Before we just "faked" this by changing the parameter's description
only, but that meant that the old name was permenantly stuck and
had to be used in qgis_process or when calling the model via
python.
as "basemap" layers
This flag identifies if the layer is considered a 'basemap' layer, where
certain properties of the layer should be ignored when calculating
project-level properties. For instance, the extent of basemap layers
should be ignored when calculating the overall extent of a project,
as these layers are typically global and extend outside of a project's
area of interest.
must be refreshed whenever the item is refreshed
This behaviour is not automatic. The new flag allows items to opt-in,
so that their children WILL be automatically refreshed when the
item is refreshed.
Should be used sparingly only to avoid expensive work
Pass widget as parent to the dialog to avoid "orphaned" child dialogs. The widget is passed as parent to QgsFeatureAction. When creating a dialog the widget is passed as parent to the dialog and the dialog is set as parent to the QgsFeatureAction (last like before).
To avoid confusion with opened dialogs the parent's visibility is set to hidden, when child dialog is opened.
This fixes#47193
these are always gracefully caught
Avoids some unwanted "unhandled exception" message boxes which
can pop up while moving the mouse around outside of the valid bounds
of the current map projection
