21.10.2015, 17:15, "Nuno Santos" :
> I think neither QSharedMemory or WorkerScript will fit in this case.
>
> Let me try to explain it better. Lets suppose I have the following basic
> model class
>
> class Model {
> QML_PROPERTY ListOfTypeA
> …
>
> QList _listOfTypeA
> }
>
> where
>
> class Typ
I think neither QSharedMemory or WorkerScript will fit in this case.
Let me try to explain it better. Lets suppose I have the following basic model
class
class Model {
QML_PROPERTY ListOfTypeA
…
QList _listOfTypeA
}
where
class TypeA {
QML_PROPERTY ListOfTypeB
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
movi
I think I have never used that.
Can you point me some examples and/or documentation?
Thanks for your reply,
Regards,
--
Nuno Santos
No dia 21/10/2015, às 14:01, Konstantin Tokarev escreveu:
>
>
> 21.10.2015, 13:28, "Nuno Santos" :
>> Hi,
>>
>> I have been building a complex UI based on a
21.10.2015, 13:28, "Nuno Santos" :
> 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
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
m
