18#ifndef QGSPROCESSINGREGISTRY_H
19#define QGSPROCESSINGREGISTRY_H
77 QList<QgsProcessingProvider *>
providers()
const {
return mProviders.values(); }
102 bool removeProvider(
const QString &providerId );
115 QList< const QgsProcessingAlgorithm *> algorithms()
const;
223 void addAlgorithmAlias( const QString &aliasId, const QString &actualId );
349 QMap< QString, QString > mAlgorithmAliases;
Abstract base class for processing algorithms.
Contains information about the context in which a processing algorithm is executed.
A registry for default styles to apply to layers generated by Processing.
Base class for providing feedback from a processing algorithm.
A post-processor for result layers created by Processing algorithms.
Base class for the definition of processing outputs.
Base class for the definition of processing parameters.
Makes metadata of processing parameters available.
Abstract base class for processing providers.
QgsProcessingRegistry & operator=(const QgsProcessingRegistry &other)=delete
void parameterTypeAdded(QgsProcessingParameterType *type)
Emitted when a new parameter type has been added to the registry.
friend class TestQgsProcessing
void parameterTypeRemoved(QgsProcessingParameterType *type)
Emitted when a parameter type has been removed from the registry and is about to be deleted.
QgsProcessingRegistry(QObject *parent=nullptr)
Constructor for QgsProcessingRegistry.
QList< QgsProcessingProvider * > providers() const
Gets list of available providers.
void providerAdded(const QString &id)
Emitted when a provider has been added to the registry.
QgsProcessingRegistry(const QgsProcessingRegistry &other)=delete
void providerRemoved(const QString &id)
Emitted when a provider is removed from the registry.
Handles results output by Processing algorithms.
As part of the API refactoring and improvements which landed in the Processing API was substantially reworked from the x version This was done in order to allow much of the underlying Processing framework to be ported into allowing algorithms to be written in pure substantial changes are required in order to port existing x Processing algorithms for QGIS x The most significant changes are outlined not GeoAlgorithm For algorithms which operate on features one by consider subclassing the QgsProcessingFeatureBasedAlgorithm class This class allows much of the boilerplate code for looping over features from a vector layer to be bypassed and instead requires implementation of a processFeature method Ensure that your algorithm(or algorithm 's parent class) implements the new pure virtual createInstance(self) call