to a horizontal scrolling action instead of vertical
This matches the same behaviour exposed by LibreOffice, and provides
a convenient way to quickly horizontally scroll tables when a mouse
doesn't have a dedicated horizontal scroll wheel.
Sponsored by the City of Canning
Instead of forcing all steps in the batch processing dialog to execute
in the main thread, we now run each step as a separate task whenever
possible. This keeps the UI nice and responsive, and permits
responsive cancelation and progress reporting.
Individual steps are still run sequentially, not in parallel (yet!)
This provider has been marked deprecated and hidden from the UI
for a number of QGIS releases. No maintainers have stepped up
to take over maintainance of this provider, and accordingly it
is now subject for removal.
* make QgsMapToolCapture capable of capturing point/line/polygons
This moves part of the code from QgsMapToolDigitizeFeature to QgsMapToolCapture so the tool can actually capture point, line and polygons. It's mainly the 'cadCanvasReleaseEvent` which has been transfered.
* use a current CaptureTechnique in QgsMapToolCapture
QgisApp has been adapted to switch between the different techniques
* add point/line/polygon specific handlers for capture map tool
* convert add part map tool to use QgsMapToolCapture capabilities
* fix use of deprecated methods
* also create a virtual handler for QgsMapToolDigitizeFeature::featureDigitized
* more dox
* use const abstract geom in virtual handlers
* add new class QgsMapToolCaptureLayerGeometry to handle layer specific operation in capture map tool
such as avoiding intersections
* allow to add linear geometries on curved geometry layers
* make actions exclusive
* add settings registry to app
* add a registry for shape map tools
* abstract class for shape map tools
* adapt QgsMapToolCapture to correctly support shape map tools
* clean up of QgisApp
* new class QgsMapToolsDigitizingTechniqueManager to handle actions in app related to capture map tools
* clean up QgisInterface
* sipify
* refactoring of existing shape tools
* refactor add ring to fully support capture map tool
* add missing folder to Doxygen
* fix layout
* fix erasing at iterator pos
* fix unused warning
* fix more dox
* fix cpp check warning
* fix unused warning
* fix annotation map tool does not support shape + set tool name
* correctly handle case when the capture is not done on a vector layer (annotation, mesh, …)
* enable shapes in annotation map tool
* correctly undo and clean
* adapt existing shape tests
the deletion test with circular vertices has been dropped since the capture map tool behaves differently
* fix warning
* refactor fill ring to support shape digitizing
* fix win build
* fix more tests
* avoid detach warnings
* fix app test + clean up
* harmonize new settings with existing ones
* fix categories
* support adding multi lines as a part
* fix adding curve part to multi line
* also handle points
* code a bit clearer
* cast not always valid
* allow adding curved polygon to multipolygon
* add test for QgsGeometry::addPart with curved parts on non-curved geoms (lines and polygons)
* fix with Python < 3.9
* better dox for deprecated interface actions methods
* remove files leftover
* remove leftover circular string curve point tool
* add default Z/M values when calling QgsGeometry::coerceToType
* Apply suggestions from code review
Co-authored-by: Nyall Dawson <nyall.dawson@gmail.com>
* fixes from review
* move layer specific part to specific tool
* fix typo
* fix leak
* fix dox
* fix segmentization
* call map tool implementation of addCurve when adding trace curve to avoid point duplication
* call sub-class implementation
* fix since 3.24 -> 3.26
* fix test
* add test to avoid extra curves when using tracing
* fix headers
Co-authored-by: Nyall Dawson <nyall.dawson@gmail.com>
accepts the prompt to save the changes BUT then cancels the file dialog
asking for the destination file name, don't treat this as though the
user has opted to discard the model
- When saving a model to a file, don't require that the model already
has a name entered. Instead, if no model name has been entered then
set the model name automatically to match the selected save filename.
E.g. if the user saves the model as "Process incoming features.model3",
then the model name will be set to "Process incoming features".
- When first saving a model, IF the user HAS already entered a model
name then make the default file name suggested by the dialog match
this model name
when configuring a new algorithm
While the previous behaviour of defaulting to a static value makes
sense for things like numeric parameters, this is a very rare use
case for map layer parameters. For better new user experience we can
default instead to showing model inputs for these parameter types.
