Now it will accept arrays as well as string representations of arrays
Added a test
Fixes#16967 value relation widget with Allow multiple selection doesn't resolve the values anymore
execution on generated layers after the algorithm (or parent
model) completes
This commit adds an interface for layer post-processing handlers
for execution following a processing algorithm operation.
Post-processing of a layer will ONLY occur if that layer is set
to be loaded into a QGIS project on algorithm completion.
Algorithms that wish to set post-processing steps for generated
layers should implement this interface in a separate class
(NOT the algorithm class itself!) and implement a method
to handle the layer post-processing.
This method always runs in the main thread and can be used to
setup renderers, editor widgets, metadata, etc for the given layer.
Fixes#17961
options->color tab
This brings all of QGIS' color scheme handling to a more logical and
user-discoverable place. Previously this functionality was only
available inside the color dialog itself (i.e. users would have to start
changing a color before they could create and edit schemes)
changes
Since this is a view operation, not an edit operation, we don't
mark it as changing the project state. (Much like how loading a
doc in a word processor and scrolling to the last page isn't
changing the document state).
When INFO_FORMAT is not an image format there is no
need to make image WIDTH and HEIGHT mandatory.
2.x accepted that, 3.x raised an exception.
This is a partial fix: SRS is still mandatory because
fixing this would require a deeper refactoring and
I believe we can live with it, because SRS will be
required if filters are combined with geometry filters,
while passing a WIDTH/HEIGHT when we don't want an image
back is always useless.
A test was also added.
Creates a new QgsProxyStyle subclass of QProxyStyle which
automatically sets the base style to match the current
application style (creating a new QStyle object, since
setting the base style takes ownership). Additionally,
QgsProxyStyle correctly parents the style to a parent
widget, avoiding leaks since calling QWidget::setStyle
doesn't transfer ownership.
Fixes incorrect theme used for layer tree view since
addition of indicator icons.
When an attribute table is set to a "Layer features" source, this
allows the underlying vector layer from which to source features
to be data defined.
(All existing table attributes (column settings) are left intact,
so setting a data defined table to a layer with different fields
will result in empty columns in the table.)
Sponsored by Kartoza/Inasafe
