diff options
author | Volker Hilsheimer <volker.hilsheimer@qt.io> | 2025-07-25 14:17:23 +0200 |
---|---|---|
committer | Volker Hilsheimer <volker.hilsheimer@qt.io> | 2025-08-08 20:49:36 +0200 |
commit | aeaa7ae43e59e165d17f3726eda11fb70271d45a (patch) | |
tree | cb77dc89846f27a21c23dbeddacd10ca10e61daa /src/qmlmodels | |
parent | 641050d4421f4df301e29fefa7ecc47ac53adb8a (diff) |
We want QRangeModel to be the preferred mechanism for exposing C++ data
to QML. Ideally, it will also be a replacement for using QVariantList or
QObjectList, without the "quirks" of exposing a value type holding
references, modelData vs named roles, no write-back etc.
To make sure that the respective usage patterns don't break, add a test
for QVariantList and QObjectList, and corresponding tests that use
QRangeModel with equivalent data structures.
The test shows some unexpected and excessive calls to both data() and
setData() implementations of QRangeModel, which are QEXPECT_FAIL'ed for
now. Unrelated to this test of QRangeModel, so leaving that for a future
commit.
Pick-to: 6.10
Change-Id: I870c78d845de507dafd27f6999154a1a7ea92a1b
Reviewed-by: Fabian Kosmale <fabian.kosmale@qt.io>
Diffstat (limited to 'src/qmlmodels')
0 files changed, 0 insertions, 0 deletions