QGIS/python/core/processing/qgsprocessingregistry.sip.in

185 lines
5.5 KiB
Plaintext
Raw Normal View History

/************************************************************************
* This file has been generated automatically from *
* *
* src/core/processing/qgsprocessingregistry.h *
* *
* Do not edit manually ! Edit header and run scripts/sipify.pl again *
************************************************************************/
class QgsProcessingRegistry : QObject
{
%Docstring
2017-12-15 10:36:55 -04:00
Registry for various processing components, including providers, algorithms
and various parameters and outputs.
QgsProcessingRegistry is not usually directly created, but rather accessed through
2017-12-19 11:43:52 -04:00
:py:func:`QgsApplication.processingRegistry()`
.. versionadded:: 3.0
%End
%TypeHeaderCode
#include "qgsprocessingregistry.h"
%End
public:
QgsProcessingRegistry( QObject *parent /TransferThis/ = 0 );
%Docstring
2017-12-15 10:36:55 -04:00
Constructor for QgsProcessingRegistry.
%End
~QgsProcessingRegistry();
QList<QgsProcessingProvider *> providers() const;
%Docstring
2017-12-15 10:36:55 -04:00
Get list of available providers.
%End
bool addProvider( QgsProcessingProvider *provider /Transfer/ );
%Docstring
2017-12-15 10:36:55 -04:00
Add a processing provider to the registry. Ownership of the provider is transferred to the registry,
and the provider's parent will be set to the registry.
Returns false if the provider could not be added (eg if a provider with a duplicate ID already exists
in the registry).
2017-12-19 11:43:52 -04:00
Adding a provider to the registry automatically triggers the providers :py:func:`QgsProcessingProvider.load()`
2017-12-15 10:36:55 -04:00
method to populate the provider with algorithms.
.. seealso:: :py:func:`removeProvider`
%End
bool removeProvider( QgsProcessingProvider *provider );
%Docstring
2017-12-15 10:36:55 -04:00
Removes a provider implementation from the registry (the provider object is deleted).
Returns false if the provider could not be removed (eg provider does not exist in the registry).
.. seealso:: :py:func:`addProvider`
%End
bool removeProvider( const QString &providerId );
%Docstring
2017-12-15 10:36:55 -04:00
Removes a provider implementation from the registry (the provider object is deleted).
Returns false if the provider could not be removed (eg provider does not exist in the registry).
.. seealso:: :py:func:`addProvider`
%End
QgsProcessingProvider *providerById( const QString &id );
%Docstring
2017-12-15 10:36:55 -04:00
Returns a matching provider by provider ID.
%End
QList< const QgsProcessingAlgorithm *> algorithms() const;
%Docstring
2017-12-15 10:36:55 -04:00
Returns a list of all available algorithms from registered providers.
.. seealso:: :py:func:`algorithmById`
%End
const QgsProcessingAlgorithm *algorithmById( const QString &id ) const;
%Docstring
2017-12-15 10:36:55 -04:00
Finds an algorithm by its ID. If no matching algorithm is found, a None
is returned.
.. seealso:: :py:func:`algorithms`
2017-12-15 10:36:55 -04:00
.. seealso:: :py:func:`createAlgorithmById`
%End
QgsProcessingAlgorithm *createAlgorithmById( const QString &id, const QVariantMap &configuration = QVariantMap() ) const /TransferBack/;
%Docstring
2017-12-15 10:36:55 -04:00
Creates a new instance of an algorithm by its ID. If no matching algorithm is found, a None
is returned. Callers take responsibility for deleting the returned object.
2017-12-15 10:36:55 -04:00
The ``configuration`` argument allows passing of a map of configuration settings
to the algorithm, allowing it to dynamically adjust its initialized parameters
and outputs according to this configuration. This is generally used only for
algorithms in a model, allowing them to adjust their behavior at run time
according to some user configuration.
.. seealso:: :py:func:`algorithms`
2017-12-15 10:36:55 -04:00
.. seealso:: :py:func:`algorithmById`
%End
void addParameterType( QgsProcessingParameterType *type );
%Docstring
Register a new parameter type for processing.
Will emit parameterTypeAdded
.. seealso:: :py:func:`removeParameterType`
.. versionadded:: 3.2
%End
void removeParameterType( QgsProcessingParameterType *type );
%Docstring
Unregister a custom parameter type from processing.
Will emit parameterTypeRemoved
.. seealso:: :py:func:`addParameterType`
.. versionadded:: 3.2
%End
QgsProcessingParameterType *parameterType( const QString &id ) const;
%Docstring
Return the parameter type registered for ``id``.
.. versionadded:: 3.2
%End
QList<QgsProcessingParameterType *> parameterTypes() const;
%Docstring
Return a list with all known parameter types.
.. versionadded:: 3.2
%End
signals:
void providerAdded( const QString &id );
%Docstring
Emitted when a provider has been added to the registry.
%End
void providerRemoved( const QString &id );
%Docstring
Emitted when a provider is removed from the registry
%End
void parameterTypeAdded( QgsProcessingParameterType *type );
%Docstring
Emitted when a new parameter type has been added to the registry.
.. versionadded:: 3.2
%End
void parameterTypeRemoved( QgsProcessingParameterType *type );
%Docstring
Emitted when a parameter type has been removed from the
registry and is about to be deleted.
.. versionadded:: 3.2
%End
private:
QgsProcessingRegistry( const QgsProcessingRegistry &other );
};
/************************************************************************
* This file has been generated automatically from *
* *
* src/core/processing/qgsprocessingregistry.h *
* *
* Do not edit manually ! Edit header and run scripts/sipify.pl again *
************************************************************************/