| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
QHashedString and QStringHash are different things.
Change-Id: Ifcac58ef41bf15dd6172fa0c42b86eca385c2ce0
Reviewed-by: Lars Knoll <lars.knoll@qt.io>
|
| |
|
|
|
|
|
|
|
|
| |
Pure QML types do not have a meta object hierarchy associated with them.
The test is only supposed to test C++ types, though. We can ignore the
types without meta objects.
Change-Id: I2a40bc0023f6d335c4dbdbc04818da60f47d8787
Fixes: QTBUG-72637
Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
|
|
|
Properties of C++ types registered with QML need to be either marked
CONSTANT or have a NOTIFY signal to be usable in property bindings.
A property which is neither CONSTANT not NOTIFYable will trigger a
runtime warning when being used in a property binding and might not
work as expected at all, see QTBUG-62913
This test reports these potentially problematic properties in two ways:
1) Report the QML type and its specific properties, i.e. the properties
defined in the C++ type that got registered for this type. Does not
include properties of base classes
2) Report all properties by defininf C++ class and list which QML type
is affected by it, i.e. which QML type has this property, inherited
or locally defined
Task-number: QTBUG-63120
Change-Id: Ie808835d86f87ca7c056fb20aae1ed7b182ea191
Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
|
