The QItemEditorCreatorBase class provides an abstract base class that must be subclassed when implementing new item editor creators. More

Inheritance diagram of PySide6.QtWidgets.QItemEditorCreatorBase

Detailed Description

QItemEditorCreatorBase objects are specialized widget factories that provide editor widgets for one particular QVariant data type. They are used by QItemEditorFactory to create editors for QStyledItemDelegate s. Creator bases must be registered with registerEditor() .

An editor should provide a user property for the data it edits. QItemDelagates can then access the property using Qt’s meta-object system to set and retrieve the editing data. A property is set as the user property with the USER keyword:

Q_PROPERTY(QColor color READ color WRITE setColor USER True)

If the editor does not provide a user property, it must return the name of the property from valuePropertyName() ; delegates will then use the name to access the property. If a user property exists, item delegates will not call valuePropertyName() .

QStandardItemEditorCreator is a convenience template class that can be used to register widgets without the need to subclass QItemEditorCreatorBase .

class PySide6.QtWidgets.QItemEditorCreatorBase


Return type


Returns an editor widget with the given parent.

When implementing this function in subclasses of this class, you must construct and return new editor widgets with the parent widget specified.

Return type


Returns the name of the property used to get and set values in the creator’s editor widgets.

When implementing this function in subclasses, you must ensure that the editor widget’s property specified by this function can accept the type the creator is registered for. For example, a creator which constructs QCheckBox widgets to edit boolean values would return the checkable property name from this function, and must be registered in the item editor factory for the Bool type.

Note: Since Qt 4.2 the item delegates query the user property of widgets, and only call this function if the widget has no user property. You can override this behavior by reimplementing setModelData() and setEditorData() .

See also

userProperty() registerEditor()