Commit daf6aa16 authored by Ulf Hermann's avatar Ulf Hermann
Browse files

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: default avatarKai Koehne <kai.koehne@digia.com>
parent 3dbc5930
...@@ -56,7 +56,6 @@ Item { ...@@ -56,7 +56,6 @@ Item {
function getDescriptions() { function getDescriptions() {
bindingTrigger = -bindingTrigger; bindingTrigger = -bindingTrigger;
backgroundMarks.requestPaint();
if (!visible) if (!visible)
return; return;
......
...@@ -80,6 +80,7 @@ Rectangle { ...@@ -80,6 +80,7 @@ Rectangle {
// Clear if model is empty. // Clear if model is empty.
if (qmlProfilerModelProxy.getState() === 0) if (qmlProfilerModelProxy.getState() === 0)
root.clear(); root.clear();
backgroundMarks.requestPaint()
} }
onDataAvailable: { onDataAvailable: {
view.clearData(); view.clearData();
...@@ -88,6 +89,8 @@ Rectangle { ...@@ -88,6 +89,8 @@ Rectangle {
qmlProfilerModelProxy.traceDuration()/10); qmlProfilerModelProxy.traceDuration()/10);
view.requestPaint(); view.requestPaint();
} }
onExpandedChanged: backgroundMarks.requestPaint()
onRowHeightChanged: backgroundMarks.requestPaint()
} }
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment