These renders were actually wrong -- instead of the whole map item
having transparency, they had transparency applied for each
individual component of the layout map (ie you could incorrectly
see parts of overlapped layers)
the path to the local QGIS git folder
When set, update all paths in the report to correspond to this
git folder. This allows the test reports downloaded from github
to be easily updated to point to local git checkouts, instead
of the hardcoded git paths from the github workflow.
to QGIS source code file
Makes the HTML report a bit more self-contained, and unbreaks
this script when viewing report artifacts from github
(image paths are still broken, though!)
This allows it to be used by other pending tasks from the task manager
while the proxied operation is pending (since the proxy progress task
thread isn't actually DOING anything while this happens)
This avoids conflicts with Qt3D framework. As noted in
https://github.com/qgis/QGIS/issues/50067#issuecomment-1318081784
"The constructor and destructor of QChangeArbiter require the use of
**every** thread in the Qt thread pool."
This causes hangs when exporting layouts containing 3d maps. We
have threads from task manager in use from elsewhere, so the
application deadlocks waiting for every thread to be freed so
that QChangeArbiter can do its thing.
So, use a new dedicated thread pool for task manager's exclusive
use. This avoids the hang when exporting 3d maps as it avoids
the deadlock between task manager and Qt3D's requirements.
(A side benefit is that we don't get delayed map rendering when
the number of queued/running tasks hits the max thread count
from the global thread pool.)
Fixes#50067
don't allow pixels which were previously non-transparent to become
totally transparent.
This can result in invisible highlights for very transparent symbols.
Fixes#54830
When loading a project which contains a 3D view, the 3D axis is not
visible even when it is supposed to be displayed. This is because the
min and max viewport ratio settings are always equal to 0 on a saved
project. Indeed, these settings are supposed to handle the 3D axis
visibility when the 3D view size changes: the axis are hidden when the
view becomes too small.
These ratio are stored as double between 0 and 1. However, the logic
which reads these parameters from a saved
project (`Qgs3DAxisSettings::readXml`) parses them as
integer. Therefore, the min and max ratio are always equal to 0. Then,
the 3D axis visibility test is always false and the 3D axis are always
hidden.
This issue is fixed by changing `Qgs3DAxisSettings::readXml` to read
the ratios as double.
