Qt wiki will be updated on October 12th 2023 starting at 11:30 AM (EEST) and the maintenance will last around 2-3 hours. During the maintenance the site will be unavailable.

How to expose lists to QML

From Qt Wiki
Jump to navigation Jump to search
This article may require cleanup to meet the Qt Wiki's quality standards. Reason: Auto-imported from ExpressionEngine.
Please improve this article if you can. Remove the {{cleanup}} tag and add this page to Updated pages list after it's clean.


English Ελληνικά

How to expose lists to QML

Which class to use?

QDeclarativeListProperty allows you to expose list like properties to QML. When implementing the function pointers in this class, memory management will be taken care of for you and the bindings will work correctly as well. Using a standard QList instead of QDeclarativeListProperty, will not take care of memory management and can cause your application to leak. In addition QList does not provide notification signals when children change. So when simply using a QList, the bindings won't work properly either. QDeclarativeListProperty is hence the recommended class to use for lists in QML.

Which constructor to use?

QDeclarativeListProperty provides 2 constructors. The first one taking a QList is there for convenience and should only be used for prototyping since it does not clean up memory for you. It still connects up the bindings properly and is therefore recommended over using a simple QList.

The second QDeclarativeListProperty constructor constructs a QDeclarativeListProperty from a set of operation functions. It works by passing functions to be called when appending, clearing, counting and getting the current position, but only the append function is necessary to implement. This is the constructor you should use in production code.

Example on how to use QDeclarativeListProperty

The following example shows how the QDeclarativeListProperty::AppendFunction and QDeclarativeListProperty::ClearFunction can be implemented:

#include <QtGui>
#include <QtDeclarative>

class MyObject : public QObject
{
    Q_OBJECT
    Q_PROPERTY(QDeclarativeListProperty<MyObject> getInfo READ getInfo CONSTANT)
public:
    MyObject()
    {}
    
    ~MyObject()
    {}
    QDeclarativeListProperty<MyObject> getInfo()
    {
        for (int i = 0; i < 10; ++i)
        {
            list << new MyObject();
        }
        return QDeclarativeListProperty<MyObject>(this, 0, &MyObject::appendObject, 0, 0, &MyObject::clearObject);
    }
    static void appendObject(QDeclarativeListProperty<MyObject> *l, MyObject *obj)
    {
        MyObject object = qobject_cast<MyObject>(l->object);
        if (object)
            object->list << obj;
    }
    static void clearObject(QDeclarativeListProperty<MyObject> *l)
    {
        MyObject object = qobject_cast<MyObject>(l->object);
        if (object) {
            foreach (MyObject o, object->list) {
                delete o;
                object->list.clear();
            }
        }
        QList<MyObject> list;
    }
}; 

#include "main.moc" 

int main(int argc, char** argv)
{
    QApplication app(argc, argv);
    QDeclarativeView view;
    qmlRegisterType<MyObject>("QtQuick", 1, 0, "MyObject");
    view.setSource(QUrl::fromLocalFile("test.qml"));
    view.show();
    return app.exec();
}

Due to the way that QDeclarativeListProperty works it is necessary to keep the QList around while the property is valid which is why it is a member of the class here.

The following QML file shows how the class above can be used and cleared in qml.

import QtQuick 1.0 

Rectangle {
    id: page
    width: 500; height: 200
    color: "red" 
    
    MyObject
    {
        id: myObject
        Component.onCompleted: {
            print("completed…", myObject.getInfo);
            
            for (var i=0; i<100; ++i) {
                myObject.getInfo = [];
            }
        }
    }
}

Note that in order to clear it, it is necessary to do:

myObject.getInfo = []

as Javascript doesn't know when to clear it otherwise.

The Qt documentation provides the following example that can be useful to have a look at as well.

Dynamic alteration of lists

Dynamic alteration of lists is not well supported right now, due to issues with bindings and lists. The current way to alter a list is to assign a new list in its place.