[Interest] QML and Threads

[Jérôme Godbout]

You were probably aware of that but just in case, you may want to take a
look at Worker Script:
http://doc.qt.io/qt-5/qml-workerscript.html

or other Qt multi threading:
http://doc.qt.io/qt-5/threads-technologies.html

We made a parallel QQmlEngine with it's own Qml objects tree and cloning or
moving object between them. I don't recommend it, it was painful regarding
Qml singleton (from qmldir singleton are not created by engine, C++ one on
the other hand can be created properly) and some others minor things.
Performance wise you need a lot of processing to be worth it. But Worker
Script may be what you are looking for, sadly only basic type can be
exchange between the working scripts.



On Wed, Oct 21, 2015 at 9:01 AM, Konstantin Tokarev <annulen at yandex.ru>
wrote:

>
>
> 21.10.2015, 13:28, "Nuno Santos" <nunosantos at imaginando.pt>:
> > Hi,
> >
> > I have been building a complex UI based on a data model that didn’t
> required threading. All the things could happen in the UI thread.
> >
> > Now I’m adding to that model a functionality that works under time
> critical events that can’t be compromised by UI interactions. This is
> specially true on mobile devices where the computing power is not abundant.
> >
> > As far as I know and from my testings, I can't expose to QML objects
> that are on a different than the GUI.
> >
> > Before advancing to a major refactor where all the time sensitive parts
> are running on a different thread and asynchronously updating it’s state to
> the UI thread, I would like to have your opinion about it.
> >
> > Is this my only option? Keep a clone model of my data on a different
> thread and respond to it’s updates on the UI thread?
>
> You may want to use shared memory to avoid cloning of data.
>
>
> --
> Regards,
> Konstantin
> _______________________________________________
> Interest mailing list
> Interest at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20151021/40950a8a/attachment.html>