21.10.2015, 13:28, "Nuno Santos" <nunosan...@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@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
