to the direct getters/setters, correctly use the explicit getters and
setters wherever possible.
Makes the code easier to read and more consistent -- now params should
only ever be used for "extra", context specific stuff instead of
commonly user authentication parameters.
* [feature] support datasets with data defined on faces in mesh calculator, fix#30219, fix#30170
added "driver" and "group name" to the calculator interface.
MDAL now supports 3 drivers for storing results, so user must be able to choose appropriate driver and dataset group name (some drivers store multiple groups to 1 file)
since then would be aliases and upper-/lower case written fieldnames be accepted in
extensions and avoid a crash in getSpatialiteFieldNameFromUserVisibleName
instead of using only one ThreadPoolExecutor for all MetaTiles, its now handled in a loop and new ThreadPools for the next zoom level will be started when all work for the previous one is already done. i guess, this will fix the issues and interferences described in #32471 and shouldn't be much slower.
but show a huge obnoxious "NOT OFFICIALLY SUPPORTED" warning
SAGA 7.3 is the new SAGA LTR, so we eventually need to move towards this.
But adding full support is going to be a painstaking tedious process. So
allow users to use this combination, but totally at their own risk.
TODO: Make SAGA provider a 3rd party plugin only and save QGIS core dev sanity ;)
be shown to users when using that provider
This can be used to return a translated warning message which should be
shown to users of this provider. It's intended for use in cases such as
a provider which relies on a 3rd-party backend, where the version of the
backend software is not officially supported, or for alerting users to
providers in a "beta" or "untrustworthy" state.
- For project : check visible state for embedded layers inside an unchecked group, instead of putting all layers in embedded-invisible-layers
- For theme : Add an 'checked-group-node' to save group visible state independently to layers in it.
Fixes#33097
support in WMS and other providers
These providers rely on the QgsDataSourceUri param methods for storing and retrieving
authentication details, so the change made to use the dedicated username/password/auth
setters in 89de7579 broke all auth support for these providers.
Ensure that the param system is fully compatible and aliased to the dedicated
username/password/authcfg getters and setters
