On 27/11/2019 11:39, Milian Wolff wrote:
Personally, I hope the answer is that this will remain supported. The only disadvantage is the runtime type introspection, which should/could be solved via Ulf's idea of something like an inline interface/trait component. Such that eventually we can do something like:``` interface ModelData { // syntax is open, just to give an idea required property string text required property int answer } delegate: Text { required property ModelData model // model is a misnomer, but I digress text: model.text + model.answer } ```
Yes, I totally get this part. But I'm asking specifically about the future of "required property var model" bit, at least for two good reasons:
1) the sake of porting existing code, and/or 2) in case the above doesn't materialize for 6.0I think I completely misunderstood something during the session and thus my question here :)
Thanks, -- Giuseppe D'Angelo | giuseppe.dang...@kdab.com | Senior Software Engineer KDAB (France) S.A.S., a KDAB Group company Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com KDAB - The Qt, C++ and OpenGL Experts
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
