QmlProfiler: manage server-side start tracing message

also
QmlProfiler: refactor eventlist state

If unexpected data is received, assuming server stopped profiling.
Also, introducing a eventlist state instead of relying on
signals sent around.  This is part of a coming bigger patch
where the profiler client is refactored.

Change-Id: Ibed9007903956daf03cc0fcb90f77b5ad2d3cf90
Reviewed-by: Kai Koehne <kai.koehne@nokia.com>

src/plugins/qmlprofiler/qml/MainView.qml

@@ -111,23 +111,29 @@ Rectangle {
                 root.progress = 0;
             }
         }
-
-        onProcessingData: {
-            root.dataAvailable = false;
-        }
-
-        onPostProcessing: {
-            root.progress = 0.9; // jump to 90%
-        }
-
-        onDataReady: {
-            if (eventCount > 0) {
+        onStateChanged: {
+            switch (qmlEventList.getCurrentStateFromQml()) {
+            case 0: {
+                root.clearAll();
+                break;
+            }
+            case 1: {
+                root.dataAvailable = false;
+                break;
+            }
+            case 2: {
+                root.progress = 0.9; // jump to 90%
+                break;
+            }
+            case 3: {
                 view.clearData();
                 progress = 1.0;
                 dataAvailable = true;
                 view.visible = true;
                 view.requestPaint();
                 zoomControl.setRange(qmlEventList.traceStartTime(), qmlEventList.traceStartTime() + qmlEventList.traceDuration()/10);
+                break;
+            }
             }
         }
     }