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

QmlProfiler: Fix some misspellings of "Flame Graph"

Browse Source 
Change-Id: I281b327eeb53d1159b165f72abee7ebe442a68ff
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io>
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
This commit is contained in:
Ulf Hermann
2016-07-18 11:25:57 +02:00
parent e5835bb885
commit 11af2f487f
2 changed files with 5 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
doc/src/analyze/qtquick-profiler.qdoc
View File

@@ -556,12 +556,12 @@
\section2 Visualizing Statistics as Flame Graphs
The \uicontrol Flamegraph view shows a more concise statistical overview
The \uicontrol {Flame Graph} view shows a more concise statistical overview
of QML and JavaScript execution. The horizontal bars show the amount of
time all invocations of a certain function took together, relative to the
total runtime of all JavaScript and QML events. The nesting shows which
functions were called by which other ones. Mind that, unlike the
\uicontrol Timeline view, the \uicontrol Flamegraph view does not show the
\uicontrol Timeline view, the \uicontrol {Flame Graph} view does not show the
time spans when no QML or JavaScript is running at all. Thus, it is not
suitable for analyzing per frame execution times. However, it is very easy
to see the total impact of the various QML and JavaScript events there.

4
src/plugins/qmlprofiler/flamegraphview.cpp
View File

@@ -39,7 +39,9 @@ FlameGraphView::FlameGraphView(QmlProfilerModelManager *manager, QWidget *parent
QmlProfilerEventsView(parent), m_content(new QQuickWidget(this)),
m_model(new FlameGraphModel(manager, this))
{
setWindowTitle(QStringLiteral("Flamegraph"));
setWindowTitle(QStringLiteral("Flame Graph"));
// We cannot change this without breaking the settings.
setObjectName(QStringLiteral("QmlProfilerFlamegraph"));
qmlRegisterType<FlameGraph>("FlameGraph", 1, 0, "FlameGraph");