In Qt Quick, models support a "modelData" property. Depending on the underlying data structure, that property holds the data stored. For a QObjectList, it is the QObject, allowing QML code to access properties of individual QObject instances in that list. As of now, this is the only way for QML code to respond to changes of properties in such a backend data structure, as nothing connects the propertyChanged-signals of all QObject entries to the dataChanged() signal of an internal QAIM proxy. And even if we can find a way to do this in QRangeModel, it will be rather expensive if only a few properties are actually interesting. So we can assume that there is code out there doing exactly this. For QRangeModel to fully replace this use case, we have to provide access to the QObject that represents a multi-role item. We can fake the modelData role to return the QObject (or gadget) instance that backs the item and a given index. For QML to see the role, we include it in the automatically generated roleNames() mapping, using a new, undocumented value in Qt::ItemDataRole. We skip that role for itemData. We do not allow setting the data for that role, as it would make object ownership very messy, so return early from such calls of setData(), and ignore an entry for that role in setItemData. Pick-to: 6.10 Change-Id: Iaf7dee5d6be18cf8b99ce796b9314459dffcfcb8 Reviewed-by: Artem Dyomin <artem.dyomin@qt.io>