Remove responsibility for credentials mutex locking from external
callers and handle appropriate locks internally. This allows the
mutex lock to be much "tighter" and avoids deadlocks when
credentials are requested while an existing credentials dialog
is being shown.
(No mutex is required protecting the credentials dialog itself
as this is ALWAYS shown in the main thread)
Fixes#20826
- unlock feature on right-click in an empty area
- allow selection of locked feature by right-click on polygon interior
(in addition to polygon rings)
- highlight polygons when mouse moves in their interior - this should also
decrease the blinking effect as the highlight is more consistent
These servers can be sloooooooow, and unpredictable.
The previous preview job may have been fast to render,
but the next may take minutes or worse to download...
With recent changes in QgsNetworkAccessManager this should be
safe to resurrect (fingers crossed!). Also simplify code a lot,
because now QgsNetworkAccessManager handles waking the worker
thread after the auth request is handled.
Add a lot more tests
races and crashes when auth requests occur in non-main thread
Like the recent SSL error handling, this commit abstracts out
the network authentication handling into a thread safe approach.
Connect the cancel rendering signal to the iteration cancelation.
This allows providers (e.g. WFS, AFS) to abort slow network requests
when they have been triggered by a render request and that request
is no longer required.
Allows much faster quit, render cancelation when using WFS/AFS layers.
Brings back QGIS 2.18's ability to directly convert a Processing model
to an equivalent Processing Python script algorithm, correctly
updated and working in the 3.x API.
Available from the model dialog, and from the right-click context
menu on an existing model.
Sponsored by Solspec