On Thursday 25. September 2014 09.44.51 Nils Jeisecke wrote:
> Hi Simon,
>
> thank you very much for the explanation. No need for bug hunting then.
>
> On Thu, Sep 25, 2014 at 7:55 AM, Simon Hausmann
>
> wrote:
> > We've changed this in Qt 5.4 slightly: When
> > converting a JavaScript object b
Hi Simon,
thank you very much for the explanation. No need for bug hunting then.
On Thu, Sep 25, 2014 at 7:55 AM, Simon Hausmann
wrote:
> We've changed this in Qt 5.4 slightly: When
> converting a JavaScript object back to a QVariant, we won't try to "destroy"
> it but instead we'll give you a Q
On Wednesday, September 24, 2014 07:02:32 PM Nils Jeisecke wrote:
> Hi!
>
> While porting to Qt5 I've stumbled over a very strange problem.
>
> QVariantMap objects mutate when transported from C++ via Qml back to C++.
>
> QVariant as constructed on the C++ side:
> QVariant(QVariantMap, QMap(("x"
Hi!
While porting to Qt5 I've stumbled over a very strange problem.
QVariantMap objects mutate when transported from C++ via Qml back to C++.
QVariant as constructed on the C++ side:
QVariant(QVariantMap, QMap(("x", QVariant(QStringList, ("a", "b")) ) ) )
QVariant when gone through Qml and hand
