Hi, We haven't made the fix, so there are currently no details to point to. But, basically, we will introduce a new "property var" syntax that behaves as you want, and deprecate "property variant". We can't simply change the behavior of "property variant" as existing applications may (probably unintentionally) depend on it's current semantics.
Cheers, Aaron On 07/06/2011, at 9:35 PM, "ext Ville M. Vainio" <[email protected]> wrote: > Thank you. Do you have a pointer to the details of the fix? Or will it > just be about "property variant" storing the reference in expected > fashion? > > On Tue, Jun 7, 2011 at 10:50 AM, <[email protected]> wrote: >> Hi, >> >> This will be fixed in QtQuick 2. >> >> Cheers, >> >> Aaron >> >> On 07/06/2011, at 5:32 PM, ext Ville M. Vainio wrote: >> >>> Re-sending to qt-qml mailing list (perhaps it should be used instead >>> of Qt5 feedback for QML language discussion? >>> >>> On Sun, Jun 5, 2011 at 2:25 PM, Ville M. Vainio <[email protected]> wrote: >>>> Currently, it's not possible to store references to javascript objects >>>> (Array, Object, functions...) in QML properties (yes, "propery >>>> variant" can't hold a js reference). I believe the rationale for this >>>> is that you can't use javascript references in property bindings. >>>> >>>> Will there be a fix for this in Qt Quick 2? >>>> >>> _______________________________________________ >>> Qt-qml mailing list >>> [email protected] >>> http://lists.qt.nokia.com/mailman/listinfo/qt-qml >> >> _______________________________________________ Qt-qml mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt-qml
