This section contains snippets that were automatically translated from C++ to Python and may contain errors.

The Property System#

An overview of Qt’s property system.

Qt provides a sophisticated property system similar to the ones supplied by some compiler vendors. However, as a compiler- and platform-independent library, Qt does not rely on non-standard compiler features like __property or [property]. The Qt solution works with any standard C++ compiler on every platform Qt supports. It is based on the Meta-Object System that also provides inter-object communication via signals and slots .

Requirements for Declaring Properties#

To declare a property, use the Q_PROPERTY() macro in a class that inherits QObject .

Q_PROPERTY(type name
           (READ getFunction [WRITE setFunction] |
            MEMBER memberName [(READ getFunction | WRITE setFunction)])
           [RESET resetFunction]
           [NOTIFY notifySignal]
           [REVISION int | REVISION(int[, int])]
           [DESIGNABLE bool]
           [SCRIPTABLE bool]
           [STORED bool]
           [USER bool]
           [BINDABLE bindableProperty]

Here are some typical examples of property declarations taken from class QWidget .

Q_PROPERTY(bool focus READ hasFocus)
Q_PROPERTY(bool enabled READ isEnabled WRITE setEnabled)
Q_PROPERTY(QCursor cursor READ cursor WRITE setCursor RESET unsetCursor)

Here is an example showing how to export member variables as Qt properties using the MEMBER keyword. Note that a NOTIFY signal must be specified to allow QML property bindings.

    Q_PROPERTY(QColor color MEMBER m_color NOTIFY colorChanged)
    Q_PROPERTY(qreal spacing MEMBER m_spacing NOTIFY spacingChanged)
    Q_PROPERTY(QString text MEMBER m_text NOTIFY textChanged)
# signals
    def colorChanged():
    def spacingChanged():
    def textChanged(newText):
# private
    QColor m_color
    qreal m_spacing
    m_text = QString()

A property behaves like a class data member, but it has additional features accessible through the Meta-Object System .

  • A READ accessor function is required if no MEMBER variable was specified. It is for reading the property value. Ideally, a const function is used for this purpose, and it must return either the property’s type or a const reference to that type. e.g., focus is a read-only property with READ function, hasFocus() . If a BINDABLE is specified, you can write READ default to have the READ accessor generated from the BINDABLE.

  • A WRITE accessor function is optional. It is for setting the property value. It must return void and must take exactly one argument, either of the property’s type or a pointer or reference to that type. e.g., enabled has the WRITE function setEnabled() . Read-only properties do not need WRITE functions. e.g., focus has no WRITE function. If you specify both a BINDABLE and WRITE default, a WRITE accessor will be generated from the BINDABLE. The generated WRITE accessor will not explicitly emit any signal declared with NOTIFY. You should register the signal as change handler to the BINDABLE, for example using Q_OBJECT_BINDABLE_PROPERTY .

  • A MEMBER variable association is required if no READ accessor function is specified. This makes the given member variable readable and writable without the need of creating READ and WRITE accessor functions. It’s still possible to use READ or WRITE accessor functions in addition to MEMBER variable association (but not both), if you need to control the variable access.

  • A RESET function is optional. It is for setting the property back to its context specific default value. e.g., cursor has the typical READ and WRITE functions, cursor() and setCursor() , and it also has a RESET function, unsetCursor() , since no call to setCursor() can mean reset to the context specific cursor. The RESET function must return void and take no parameters.

  • A NOTIFY signal is optional. If defined, it should specify one existing signal in that class that is emitted whenever the value of the property changes. NOTIFY signals for MEMBER variables must take zero or one parameter, which must be of the same type as the property. The parameter will take the new value of the property. The NOTIFY signal should only be emitted when the property has really been changed, to avoid bindings being unnecessarily re-evaluated in QML, for example. The signal is emitted automatically when the property is changed via the Qt API ( setProperty , QMetaProperty , etc.), but not when the MEMBER is changed directly.

  • A REVISION number or REVISION() macro is optional. If included, it defines the property and its notifier signal to be used in a particular revision of the API (usually for exposure to QML). If not included, it defaults to 0.

  • The DESIGNABLE attribute indicates whether the property should be visible in the property editor of GUI design tool (e.g., Qt Designer ). Most properties are DESIGNABLE (default true). Valid values are true and false.

  • The SCRIPTABLE attribute indicates whether this property should be accessible by a scripting engine (default true). Valid values are true and false.

  • The STORED attribute indicates whether the property should be thought of as existing on its own or as depending on other values. It also indicates whether the property value must be saved when storing the object’s state. Most properties are STORED (default true), but e.g., minimumWidth() has STORED false, because its value is just taken from the width component of property minimumSize() , which is a QSize .

  • The USER attribute indicates whether the property is designated as the user-facing or user-editable property for the class. Normally, there is only one USER property per class (default false). e.g., checked is the user editable property for (checkable) buttons. Note that QItemDelegate gets and sets a widget’s USER property.

  • The BINDABLE bindableProperty attribute indicates that the property supports bindings , and that it is possible to set and inspect bindings to this property via the meta object system ( QMetaProperty ). bindableProperty names a class member of type QBindable <T>, where T is the property type. This attribute was introduced in Qt 6.0.

  • The presence of the CONSTANT attribute indicates that the property value is constant. For a given object instance, the READ method of a constant property must return the same value every time it is called. This constant value may be different for different instances of the object. A constant property cannot have a WRITE method or a NOTIFY signal.

  • The presence of the FINAL attribute indicates that the property will not be overridden by a derived class. This can be used for performance optimizations in some cases, but is not enforced by moc. Care must be taken never to override a FINAL property.

  • The presence of the REQUIRED attribute indicates that the property should be set by a user of the class. This is not enforced by moc, and is mostly useful for classes exposed to QML. In QML, classes with REQUIRED properties cannot be instantiated unless all REQUIRED properties have been set.

The READ, WRITE, and RESET functions can be inherited. They can also be virtual. When they are inherited in classes where multiple inheritance is used, they must come from the first inherited class.

The property type can be any type supported by QVariant , or it can be a user-defined type. In this example, class QDate is considered to be a user-defined type.

Q_PROPERTY(QDate date READ getDate WRITE setDate)

Because QDate is user-defined, you must include the <QDate> header file with the property declaration.

For historical reasons, QMap and QList as property types are synonym of QVariantMap and QVariantList.

Reading and Writing Properties with the Meta-Object System#

A property can be read and written using the generic functions property() and setProperty() , without knowing anything about the owning class except the property’s name. In the code snippet below, the call to setDown() and the call to setProperty() both set property “down”.

button = QPushButton()
object = button
object.setProperty("down", True)

Accessing a property through its WRITE accessor is the better of the two, because it is faster and gives better diagnostics at compile time, but setting the property this way requires that you know about the class at compile time. Accessing properties by name lets you access classes you don’t know about at compile time. You can discover a class’s properties at run time by querying its QObject , QMetaObject , and QMetaProperties .

object = ...
metaobject = object.metaObject()
count = metaobject.propertyCount()
for i in range(0, count):
    metaproperty = metaobject.property(i)
    name = metaproperty.name()
    value = object.property(name)

In the above snippet, property() is used to get metadata about each property defined in some unknown class. The property name is fetched from the metadata and passed to property() to get the value of the property in the current object .

A Simple Example#

Suppose we have a class MyClass, which is derived from QObject and which uses the Q_OBJECT macro in its private section. We want to declare a property in MyClass to keep track of a priority value. The name of the property will be priority, and its type will be an enumeration type named Priority, which is defined in MyClass.

We declare the property with the Q_PROPERTY() macro in the private section of the class. The required READ function is named priority, and we include a WRITE function named setPriority. The enumeration type must be registered with the Meta-Object System using the Q_ENUM() macro. Registering an enumeration type makes the enumerator names available for use in calls to setProperty() . We must also provide our own declarations for the READ and WRITE functions. The declaration of MyClass then might look like this:

class MyClass(QObject):

    Q_PROPERTY(Priority priority READ priority WRITE setPriority NOTIFY priorityChanged)
# public
    MyClass(QObject parent = None)
    Priority = { High, Low, VeryHigh, VeryLow }
    def setPriority(priority):

        m_priority = priority

    def priority():
    { return m_priority; }
# signals
    def priorityChanged(Priority):
# private
    m_priority = Priority()

The READ function is const and returns the property type. The WRITE function returns void and has exactly one parameter of the property type. The meta-object compiler enforces these requirements.

Given a pointer to an instance of MyClass or a pointer to a QObject that is an instance of MyClass, we have two ways to set its priority property:

myinstance = MyClass()
object = myinstance
object.setProperty("priority", "VeryHigh")

In the example, the enumeration type that is the property type is declared in MyClass and registered with the Meta-Object System using the Q_ENUM() macro. This makes the enumeration values available as strings for use as in the call to setProperty() . Had the enumeration type been declared in another class, its fully qualified name (i.e., OtherClass::Priority) would be required, and that other class would also have to inherit QObject and register the enumeration type there using the Q_ENUM() macro.

A similar macro, Q_FLAG() , is also available. Like Q_ENUM() , it registers an enumeration type, but it marks the type as being a set of flags, i.e. values that can be OR’d together. An I/O class might have enumeration values Read and Write and then setProperty() could accept Read | Write. Q_FLAG() should be used to register this enumeration type.

Dynamic Properties#

setProperty() can also be used to add new properties to an instance of a class at runtime. When it is called with a name and a value, if a property with the given name exists in the QObject , and if the given value is compatible with the property’s type, the value is stored in the property, and true is returned. If the value is not compatible with the property’s type, the property is not changed, and false is returned. But if the property with the given name doesn’t exist in the QObject (i.e., if it wasn’t declared with Q_PROPERTY() ), a new property with the given name and value is automatically added to the QObject , but false is still returned. This means that a return of false can’t be used to determine whether a particular property was actually set, unless you know in advance that the property already exists in the QObject .

Note that dynamic properties are added on a per instance basis, i.e., they are added to QObject , not QMetaObject . A property can be removed from an instance by passing the property name and an invalid QVariant value to setProperty() . The default constructor for QVariant constructs an invalid QVariant .

Dynamic properties can be queried with property() , just like properties declared at compile time with Q_PROPERTY() .

Properties and Custom Types#

Custom types used by properties need to be registered using the Q_DECLARE_METATYPE() macro so that their values can be stored in QVariant objects. This makes them suitable for use with both static properties declared using the Q_PROPERTY() macro in class definitions and dynamic properties created at run-time.

Adding Additional Information to a Class#

Connected to the property system is an additional macro, Q_CLASSINFO() , that can be used to attach additional namevalue pairs to a class’s meta-object, for example:

Q_CLASSINFO("Version", "3.0.0")

Like other meta-data, class information is accessible at run-time through the meta-object; see classInfo() for details.

Using Bindable Properties#

Three different types can be used to implement bindable properties:

  • QProperty

  • QObjectBindableProperty

  • QObjectComputedProperty .

The first one is a general class for bindable properties. The latter two can only be used inside a QObject .

For more information, including examples, see the classes mentioned above and the general tips on implementing and using bindable properties .

See also

Meta-Object System Signals and Slots Q_DECLARE_METATYPE() QMetaType QVariant Qt Bindable Properties