Remove the Aspect Thread

This now makes the Qt3D simulation loop run in the Main Thread.

In theory having the Aspect Thread allowed Qt3D to continue rendering
even if the main thread got locked. In practice however this leads to
a large amount of complexities in the Qt3D implementations and provides
little value as in most cases blocking the main thread would block animations
driven by frontend nodes.

Removing the Aspect Thread will allow to remove the backend tree copies each
aspect had to make which will allow to reduce memory. In addition, getting direct
access to frontend nodes, will now be possible without introducing races which
should allow to make more optimizations and reduce latencies on some operations.

Change-Id: I80e4cd6427de06ddedfa1bb50d40710b91867b24
Reviewed-by: Mike Krus <mike.krus@kdab.com>

1 files changed, 2 insertions, 2 deletions

diff --git a/src/core/qchangearbiter_p.h b/src/core/qchangearbiter_p.h
index 1f453ff56..c7d96b593 100644
--- a/src/core/qchangearbiter_p.h
+++ b/src/core/qchangearbiter_p.h
@@ -109,8 +109,8 @@ public:
     void sceneChangeEventWithLock(const QSceneChangePtr &e) override; // QLockableObserverInterface impl
     void sceneChangeEventWithLock(const QSceneChangeList &e) override; // QLockableObserverInterface impl
 
-    Q_INVOKABLE void setPostman(Qt3DCore::QAbstractPostman *postman);
-    Q_INVOKABLE void setScene(Qt3DCore::QScene *scene);
+    void setPostman(Qt3DCore::QAbstractPostman *postman);
+    void setScene(Qt3DCore::QScene *scene);
 
     QAbstractPostman *postman() const final;
     QScene *scene() const;