The problem was that QgsSnappingConfig when initialized from a project
loads global settings from QgsSettings and sets individual layer configs
based on that.
The issue was showing up only in "current layer" mode of vertex tool
because for "all layers" mode all individual layer configs were overwritten.
... and forward all app's message bar messages to
the dialog's message bar in case it is modal and
visible.
Also adds a question dialog when a /vsicurl/
add layer operation failed and offers a chance
to try the "normal" opening mode.
in case the provider does not (WFS is one of them).
Rationale: consider that there is not such
a thing like a list of supported types for WFS
and parsing the particular describeFeatureType
for the layer would restrict the types to only
those actually existing in the layer, but
we are dealing with virtual fields here (because
WFS has no column add capabilities) so
let's give the users a minimal set of useful
types to play with.
Fixes#21086
Fixes#21091
The issue was due to the /vsicurl/ not
being able to open a streaming endpoint.
“Things are not always what they seem; the first appearance
deceives many; [...]”
― Phaedrus
And allow these to be retrieved from QgsNetworkRequestParameters.
This allows logging code to identify the area of code where a request
originated from, making debugging much easier!
Tag all requests created with appropriate class name and IDs
This signal is propagated to the main thread QgsNetworkAccessManager
instance, so it is necessary only to connect to the main thread's signal
in order to receive notifications about requests created in any thread.
Also includes the original requestId to allow linked download progress
to original request
internal symbol clones
Rendering symbols is a NON-CONST operation, which can permanently
alter the symbol instance (e.g. via changes made by the symbol
or symbol layer's startRender methods.).
This makes debugging super complex - because methods which look
like they are just generating previews of symbols can actually
change the original symbol instances, resulting in permanent changes
to a layer's style.
Refs #19910 (specifically, me pulling my hair out trying to deduce
seemingly random changes to layer's symbols)
Instead of requiring clients to generate temporary file names themselves,
(or use the cryptic "memory:" string!), this PR adds a static constant
QgsProcessing.TEMPORARY_OUTPUT
If a layer/sink output parameter is set to QgsProcessing.TEMPORARY_OUTPUT,
then the temporary output filename will be generated automatically at
algorithm run time. This means callers don't need to mess around with
finding appropriate temporary folders and paths.
Another benefit is that TEMPORARY_OUTPUT is stored in the processing
history, so if you re-run a previous algorithm which was set to
output to a temporary file, it no longer tries to use that same
previous temporary path and instead generates a new one.
because the fields in the (spatialite) cached
iterator are not the same as the main iterator.
Fix#21077 - Form Value relation based on WFS layer (nothing to do with
value relations)
This PR continues the work started in PR #8951.
This commit replaces occurences of #include "qgis.h" by #include "qgis_sip.h",
where possible = when files only depends on SIP_XXX features.
This is a simple workaround, not a real fix. The real fix is to
move the symbolModified signal out of the updatePreview call,
because we should be able to refresh a preview image without
marking it as a changed symbol. But that's higher risk, so deferred
to 3.8
