Details
-
Task
-
Resolution: Unresolved
-
P2: Important
-
6.8
-
None
Description
From the discussion at QTBUG-127650:
the logic needs to be improved for anything deriving from the propagator
- It still makes sense to warn about read-only accesses to the attached property, because they can't override the value.
- Any write access should however not trigger a warning, as that would defeat the point.
For other attached properties, this still needs some consideration. `ListView` can certainly be reused, but only as long as there is no further ListView in the hierarchy in between. For other attached properties like `Keys`, that might need a bit more investigation (does the position in the item tree affect the event handling?)
Enhance the quicklint plugin such that it can be re-enabled again.
Attachments
Issue Links
- split from
-
QTBUG-127650 Strange behaviours in QML warning, "Using attached type <TYPE> already initialized in a parent scope"
-
- Closed
-