... and to count them
Tests updated accordingly, note that from now on
the assumption that a layer store or a layer project
contains only valid layers will not be true anymore.
To be honest it has never been true, because a
layer can become invalid at any time during
its life cycle, so better never assume that a
layer from the store or from the project is vaid.
This can be used to restore initial layer status or to
apply styles and other layer properties if the data
source is changed.
The idea is that the user can fix bad layers at any time,
and by setting a new datasource she probably wants
to keep the original layer properties.
Don't override default font letter spacing or stretch -- it's not
safe to do because the results are very dependent on the individual
font's appearance and rendering hints.
Fixes#20349
in browser
With options to
- load project
- open project file properties (operating system file properties
dialog that is, on supported platforms only)
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.
There is no direct relationship between postgis SRIDs and SRIDs used in any other database.
If you imported data with GDAL, things may work, because GDAL prefers to use equivalent SRIDs
to EPSG IDs / PostGIS SRIDs.
If you imported data with QGIS, that will not work.
QGIS MS SQL provider happily uses internal SRS IDs from srs.db for SRIDs.
That should be probably modified to use GDAL's logic:
1. preferably use EPSG ID as SRID
2. if taken, find a safe SRID
These include:
- fetching incomplete (corrupted) geometries
- fetching incomplete text data (e.g. WKT for CRS)
Also fixes a bug with empty attribute table for some ms sql layers
