QmlProfiler: Move event handling into model manager

This is the logical place to do it. Adding the event first to the QML
model and then passing it back to the manager in order to have it
dispatched to the other models is somewhat backwards.

Change-Id: I64b1cb38f97331b62d83fa5ae49b9b2690810d40
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
Reviewed-by: Ulf Hermann <ulf.hermann@qt.io>

1 files changed, 6 insertions, 1 deletions

diff --git a/src/plugins/qmlprofiler/qmlprofilermodelmanager.h b/src/plugins/qmlprofiler/qmlprofilermodelmanager.h
index d26cfa4e22..bd05ab97f9 100644
--- a/src/plugins/qmlprofiler/qmlprofilermodelmanager.h
+++ b/src/plugins/qmlprofiler/qmlprofilermodelmanager.h
@@ -100,6 +100,7 @@ public:
 
     bool isEmpty() const;
     uint numLoadedEvents() const;
+    uint numLoadedEventTypes() const;
 
     int registerModelProxy();
     void announceFeatures(quint64 features, EventLoader eventLoader, Finalizer finalizer);
@@ -107,7 +108,11 @@ public:
     int numFinishedFinalizers() const;
     int numRegisteredFinalizers() const;
 
-    void dispatch(const QmlEvent &event, const QmlEventType &type);
+    void addEvents(const QVector<QmlEvent> &events);
+    void addEvent(const QmlEvent &event);
+
+    void addEventTypes(const QVector<QmlEventType> &types);
+    void addEventType(const QmlEventType &type);
 
     quint64 availableFeatures() const;
     quint64 visibleFeatures() const;