QgsCoordinateReferenceSystemRegistry
This was the last bit of untested, direct sql database access relating
to custom projections. Now everything is nice and central and protected
by unit tests.
object
Updates the definition and parameters of the coordinate reference system to their
latest values.
This only has an effect if the CRS is a user defined custom CRS, and the definition
of that custom CRS has changed. In this case the parameters of the object (such as the
proj and WKT string definitions, and other related properties) will be updated to
reflect the current definition of the custom CRS.
Any objects which store CRS objects should connect to the QgsApplication::coordinateReferenceSystemRegistry()'s
QgsCoordinateReferenceSystemRegistry::userCrsChanged() signal and call this method
on their stored CRS objects whenever the signal is emitted in order to update these
CRSes to their new definitions.
Refs #40704
to QgsApplication
In the long term all methods for retrieving available CRS details
should be moved here (instead of being scattered all over the place,
as they are now). But for now the logic for saving and updating
user CRS definitions has been moved here only.
The initial motivation is to create a central place where objects
can connect to in order to listen for when a user makes changes
to their custom projections.
Refs #40704
results as well as map layers
This extends the recent addition of smooth map updates for raster
layers to also apply to map labels. Now you'll see a scaled/transformed
version of the previous map render's labels while the new labeling
results are being generated in the background.
Avoids "flashy" redraws of map labels
map layer renderers
These renderers can then use the layer rendering time for the previous
map render job to refine their logic regarding when its appropriate
to start compositing the layer render
to QgsNetworkAccessManager, and add a checkbox in the network
logger panel to allow users to temporarily disable the network cache
This can be VERY useful when debugging QGIS network activity, or when
using QGIS to test server side changes.
This is a transient setting only, and is forgotten as soon as QGIS
is closed. That's by design -- we don't want users to accidentally
leave this enabled and cause unnecessary server load.
Store rows in the model, remove rewind and random access from
query result class.
This implementation is way simpler but the (forward) iterator
can be used only once.
I'm still convinced that the old implementation was better and more
flexible but I need to move forward.
Client code will need to store the results from the iterator.
