Update branch adn fix errors#1
Conversation
…ng and pc loading
…-error-message Fix raster calc opencl build error and add informative error message
Avoid module wide `QtConcurrent` imports
Cloned QgsRasterLayer objects in the copy constructor were never added to mRasterLayers, so the destructor's qDeleteAll(mRasterLayers) never freed them. Every clone() call (triggered by the rendering pipeline on each pan/zoom) leaked all source raster layers. Fixes qgis#64559
add merge tag for aggregate algorithm so that it shows up when searching for it
Unlike the other floater values which have a boolean hidden/visible state only, these floater values support display in either ellipsoidal or cartesian measurements. This commit adds the framework for handling these new floater item types. It's tricky to decide if the default should be ellipsoidal or cartesian measurements. Elsewhere we tend to use ellipsoidal measurements by default, but the whole CAD tools are built strictly around Cartesian measurements (eg distance constraints are always Cartesian). If we default to Ellipsoidal measurements here to match the rest of QGIS measurement tools, then users will get confused if they use a distance constraint for a set distance and then immediately see a DIFFERENT total length measurement readout! On the other hand, if we default to Cartesian measurements to match the CAD constraints, then users will get confused when the CAD floater shows a total area, and then immediately after digitizing the identify tool show will show a DIFFERENT total area! argh! So to make things as user friendly as possible, we: 1. FORCE the user to make the choice. The area and length measurements default to hidden, and to show them the user must select the floater menu, "Show Area" submenu -> and then pick between "hidden", "show cartesian area" or "show ellipsoidal area" (and similar for total length). There can be NO ambiguity as the user has explicitly made a choice between them! 2. We show a small icon next to the floater area/total distance labels, with a curved line if the measurement is ellipsoid based, or a straight line if it's cartesian based
Required to allow canvases/map tools to emit status bar messages
bar while digitizing Like the equivalent CAD float setting, these measures can be individually controlled to hide them, or show in either ellipsoidal or cartesian calculations
Contains utility functions for working with measurements
And avoid unnecessary forced conversion of text rotation to int -- the QPainter methods are capable of floating point rotation values
…tions Instead of always left aligning these, expose a control for users to choose alignment. This is especially useful for multi-line annotations, which look ugly when left aligned on the left side of the map.
And split to separate widget/dialog classes Proper cleanup cannot be done here, due to need to maintain the old Processing gui API
[tests] Add tests for QgsGeometryUtils::interpolateZ
QgsVectorFileWriter: fix writing NurbsCurve to OGR, by converting them to LineString
Fix incorrect path value when constructing QgsDataProvider
…dings' into bug_18101-python-validation-bindings # Conflicts: # src/app/gps/qgsappgpsdigitizing.cpp
# Conflicts: # python/gui/auto_additions/qgisinterface.py # python/gui/auto_generated/qgisinterface.sip.in # python/gui/gui_auto.sip
🧮 Vcpkg update reportAdded packages: Removed packages: Updated packages: 🪟 Windows Qt6 buildsDownload Windows Qt6 builds of this PR for testing. |
5018ee9
into
sewe2000:bug_18101-python-validation-bindings
Description
Updating branch from changes from
master. Also, I fixed some pre-commit errors.In PR to QGIS base repo there is an error in DB, but maybe it is unrelated - this is not addresed here.