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.
scrolling stops in some circumstances
Basically, if the user moves the mouse after scrolling the area
with the wheel, we should release the time based lock we use
to avoid unwanted widget changes mid-scroll immediately. Otherwise
it's impossible to scroll wheel->move mouse onto widget->wheel to change
widget value quickly.
This allows users to just directly enter a custom CRS definition
(from proj or wkt), instead of requiring them to add a custom
CRS to their database.
It's much friendlier for users who just want to defined a custom
projection for e.g. an overview map.
QgsProcessingParameterWidgetContext)
added a `setProject(QgsProject *project)` to QgsMapLayerModel,
QgsMapLayerProxyModel and QgsMapLayerComboBox
QgsProcessingMapLayerComboBox::setWidgetContext(...) now uses the
context project
Intended for use in storing the results of a long running operation.
E.g. a processing task would store the initial operation history
when the operation starts, and when it finishes it should update
that entry with the full log and output results.
No user visible changes, but we gain the flexibility for better
history storage, including the ability to store the outputs
calculated by the algorithm execution...!
current settings as JSON and paste json settings from clipboard
The utility of this is two fold:
1. It provides a way for users to copy the settings defined in the
dialog in a text format, so they can store these easily and then
restore later by pasting the value
2. It provides an easy way for users to copy the settings into
the json format consumed by qgis_process (following
https://github.com/qgis/QGIS/pull/46497), so that it is easy
for users to see the expected format even for complex parameters
(like tin interpolation parameters)
