Use better QmlProfiler client from Qt Creator

This client can track locations itself, and thus doesn't require the
server to send the event types over and over with each message. Once all
our client implementations have this feature we can drop a lot of code.

Furthermore, this way we can write regression tests for bugs that only
occur when client side location tracking is active.

Change-Id: I3735392452e20a7be98e92b900fadef04701d85f
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>

1 files changed, 21 insertions, 0 deletions

diff --git a/src/qml/debugger/qqmlprofilerdefinitions_p.h b/src/qml/debugger/qqmlprofilerdefinitions_p.h
index 91d0376837..f84a2c44e2 100644
--- a/src/qml/debugger/qqmlprofilerdefinitions_p.h
+++ b/src/qml/debugger/qqmlprofilerdefinitions_p.h
@@ -69,6 +69,7 @@ struct QQmlProfilerDefinitions {
         PixmapCacheEvent,
         SceneGraphFrame,
         MemoryAllocation,
+        DebugMessage,
 
         MaximumMessage
     };
@@ -161,6 +162,26 @@ struct QQmlProfilerDefinitions {
 
         MaximumInputEventType
     };
+
+    static ProfileFeature featureFromRangeType(RangeType range)
+    {
+        switch (range) {
+            case Painting:
+                return ProfilePainting;
+            case Compiling:
+                return ProfileCompiling;
+            case Creating:
+                return ProfileCreating;
+            case Binding:
+                return ProfileBinding;
+            case HandlingSignal:
+                return ProfileHandlingSignal;
+            case Javascript:
+                return ProfileJavaScript;
+            default:
+                return MaximumProfileFeature;
+        }
+    }
 };
 
 QT_END_NAMESPACE