[Interest] Ensuring that a queued invocation occurs after deferred deletion
Curtis Mitch
mitch.curtis at theqtcompany.com
Wed Mar 23 09:23:08 CET 2016
From: Sina Dogru [mailto:sinadooru at gmail.com]
Sent: Tuesday, 22 March 2016 10:09 PM
To: Curtis Mitch <mitch.curtis at theqtcompany.com>
Cc: interest at qt-project.org
Subject: Re: [Interest] Ensuring that a queued invocation occurs after deferred deletion
Hi, I saw your bug report. I encountered the same problem last week and I found a workaround by passing the properties that belong to another object one by one to JSon object. For example,
setSource("qrc:/LoaderItem.qml", { "color": theGame.player.color })
But in my case there was only one property. So instead of passing the object, passing the property was easy. But for more complicated situations that would be a pain...
Sina
----
Hi.
That’s a good work around, but you’re right in that it’s more difficult in my situation. I have a handful of objects that I need access to, each with their own objects as properties, and so on.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20160323/b698a66c/attachment.html>
More information about the Interest
mailing list