diff options
author | Andrei Golubev <andrei.golubev@qt.io> | 2021-07-23 16:53:27 +0200 |
---|---|---|
committer | Andrei Golubev <andrei.golubev@qt.io> | 2022-01-26 08:10:08 +0100 |
commit | f03f6eec9ac6467cdf601a8c056e76b3905472f3 (patch) | |
tree | eac49736e8afa364989f65423ff592fad7347771 /cmake | |
parent | 8ec6b990e13c8b41d0415af83c5890ef7a9ee227 (diff) |
Prototype private property access in tst_qmltc_manual
In theory, private properties could be supported in the compilers
through the QMetaProperty. Since we already know each C++ property's
index (and QML properties cannot be private), we can use that index
for a fast-ish QMetaProperty lookup. QMetaProperty itself has read and
write methods, which should be sufficient for all the use cases:
* read a value
* write a value
* create a binding
In fact, binding creation on non-grouped private properties is already
supported (or almost supported) since bindings already rely on
QMetaProperty information.
As a downside, QMetaProperty (even without name lookup) is still an
overkill compared to
static_cast<ClassPrivate *>(QObjectPrivate::get(this)) and then calling
READ/WRITE/etc. of a property directly
Task-number: QTBUG-91956
Change-Id: If77d2783ac161cb9bdd0bd9d0b397fe88e9c471d
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>
Diffstat (limited to 'cmake')
0 files changed, 0 insertions, 0 deletions