QmlProfiler: access the background marks from where they're created

It's considered bad style to access properties of parent objects
defined in a different component as that reduces code reusability.

Change-Id: I0dbe4a3663026d12b2666de75c93841528fe295c
Reviewed-by: Kai Koehne <kai.koehne@digia.com>

src/plugins/qmlprofiler/qml/CategoryLabel.qml

@@ -56,7 +56,6 @@ Item {
 
     function getDescriptions() {
         bindingTrigger = -bindingTrigger;
-        backgroundMarks.requestPaint();
         if (!visible)
             return;
 

src/plugins/qmlprofiler/qml/MainView.qml

@@ -80,6 +80,7 @@ Rectangle {
             // Clear if model is empty.
             if (qmlProfilerModelProxy.getState() === 0)
                 root.clear();
+            backgroundMarks.requestPaint()
         }
         onDataAvailable: {
             view.clearData();
@@ -88,6 +89,8 @@ Rectangle {
                                  qmlProfilerModelProxy.traceDuration()/10);
             view.requestPaint();
         }
+        onExpandedChanged: backgroundMarks.requestPaint()
+        onRowHeightChanged: backgroundMarks.requestPaint()
     }