> Yeah, that's going to make using QML in actual applications a whole lot > harder. For instance, sometimes access to some root node is needed even > from deep leaf files. Removing that capability is quite a drastic measure.
Yes, but the problems with this construct are the same as with generic context properties: Your QML component requires some context that it doesn't declare. Therefore your code is not reusable and brittle wrt addition of properties in other places. Mind that all those dynamic lookups will still live on in QML 2, and we will maintain QML 2 throughout Qt6. They just won't be valid in QML 3. Ulf _______________________________________________ Development mailing list [email protected] https://lists.qt-project.org/listinfo/development
