QGIS API Documentation 3.41.0-Master (25ec5511245)
|
Makes metadata of processing parameters available. More...
#include <qgsprocessingparametertype.h>
Public Member Functions | |
virtual | ~QgsProcessingParameterType ()=default |
virtual QStringList | acceptedPythonTypes () const |
Returns a list of the Python data types accepted as values for the parameter. | |
virtual QStringList | acceptedStringValues () const |
Returns a descriptive list of the possible string values acceptable for the parameter. | |
virtual QString | className () const |
Returns the corresponding class name for the parameter type. | |
virtual QgsProcessingParameterDefinition * | create (const QString &name) const =0 |
Creates a new parameter of this type. | |
virtual QString | description () const =0 |
A human readable and translatable description for this parameter type. | |
virtual Qgis::ProcessingParameterTypeFlags | flags () const |
Determines if this parameter is available in the modeler. | |
virtual QString | id () const =0 |
A static id for this type which will be used for storing this parameter type. | |
virtual QVariantMap | metadata () const |
Metadata for this parameter type. | |
virtual QString | name () const =0 |
A human readable and translatable short name for this parameter type. | |
virtual QString | pythonImportString () const |
Returns a valid Python import string for importing the corresponding parameter type, e.g. | |
Makes metadata of processing parameters available.
Definition at line 33 of file qgsprocessingparametertype.h.
|
virtualdefault |
|
virtual |
Returns a list of the Python data types accepted as values for the parameter.
E.g. "str", "QgsVectorLayer", "QgsMapLayer", etc.
These values should should match the Python types exactly (e.g. "str" not "string", "bool" not "boolean"). Extra explanatory help can be used (which must be translated), eg "str: as comma delimited list of numbers".
Definition at line 30 of file qgsprocessingparametertype.cpp.
|
virtual |
Returns a descriptive list of the possible string values acceptable for the parameter.
E.g. for a QgsProcessingParameterVectorLayer this may include "Path to a vector layer", for QgsProcessingParameterBoolean "1 for true, 0 for false" etc.
Extra explanatory help can be used (which must be translated), eg "a comma delimited list of numbers".
Definition at line 35 of file qgsprocessingparametertype.cpp.
|
inlinevirtual |
Returns the corresponding class name for the parameter type.
Definition at line 76 of file qgsprocessingparametertype.h.
|
pure virtual |
Creates a new parameter of this type.
|
pure virtual |
A human readable and translatable description for this parameter type.
This can be a longer description suitable for tooltips and other elements that give the user context for a given parameter.
|
virtual |
Determines if this parameter is available in the modeler.
The default implementation returns true
.
Definition at line 20 of file qgsprocessingparametertype.cpp.
|
pure virtual |
A static id for this type which will be used for storing this parameter type.
|
virtual |
Metadata for this parameter type.
Can be used for example to define custom widgets. The default implementation returns an empty map.
Definition at line 25 of file qgsprocessingparametertype.cpp.
|
pure virtual |
A human readable and translatable short name for this parameter type.
This will be used in comboboxes and list widgets.
|
inlinevirtual |
Returns a valid Python import string for importing the corresponding parameter type, e.g.
"from qgis.core import QgsProcessingParameterBoolean".
Definition at line 66 of file qgsprocessingparametertype.h.