These providers will be used to control how the browser data items
behave within GUI, and to allow separation of GUI related
properties of browser items from the core code.
A new registry QgsDataItemGuiProviderRegistry has been created
(modeled off QgsDataItemProviderRegistry), with an application
wide instance available from QgsGui::instance()->dataItemGuiProviderRegistry()
When adding a vertex to a segment that is coincident with some other
segments and topological editing is enabled, vertex tool will now correctly
add new vertex also the coincident segments to preserve shared borders.
When errors have been found and shown on the dock and deactivating layer checks that resulted in crashes.
Also when deactivating and reactivating checks, that would result in crashes.
Fixes the authentication database cannot be opened in some circumstances.
We need to ensure that the pooled database connection is removed
immediately on thread finalisation and cannot defer this until
the main thread event loop runs.
Fixes#20262
Allows for removal of duplicate features, identified using the values
in one (or more) field values from the input features.
Optionally any discarded (duplicate) features can be saved to a separate
sink.
within browser
Allows QGIS project file items inside the browser to be expanded,
showing the full layer tree (including groups) contained within
that project. Layers are shown as normal layer items, allowing
them to be easily added to the current project via drag and drop
or double click. Additionally, because they are treated just
the same as any other layer items in the browser, they can be
drag and dropped within the browser to e.g. directly copy the
layer to a geopackage file!
TODO: apply layer symbology from project file when adding a
layer from a different project to the current project
item creation and override default project file handling
If no provider is registered which handles QGIS project files,
then the default behavior is used as a fallback
And catch segmentation faults from GRASS commands and show a nice
helper text advising user that QGIS isn't at fault here ;)
Also add a tip to try disabling the v.external option if that setting
is enabled and a GRASS segfault occurs
