feedc0de/qt-creator
1
0
Fork 0
forked from qt-creator/qt-creator
Code Pull Requests Activity

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

Browse Source 
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>
This commit is contained in:
Ulf Hermann
2014-06-23 17:08:15 +02:00
parent 3dbc59309a
commit daf6aa160b
2 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
src/plugins/qmlprofiler/qml/CategoryLabel.qml
View File

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

3
src/plugins/qmlprofiler/qml/MainView.qml
View File

@@ -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 {
qmlProfilerModelProxy.traceDuration()/10); qmlProfilerModelProxy.traceDuration()/10);
view.requestPaint(); view.requestPaint();
} }
onExpandedChanged: backgroundMarks.requestPaint()
onRowHeightChanged: backgroundMarks.requestPaint()
} }