forked from qt-creator/qt-creator
QmlProfiler: Clear range restrictions when clearing events views
Range restrictions don't persist across profiling sessions, in contrast to feature selections. Change-Id: If98a8dae7eed3019e68e361ea69689658241d39d Reviewed-by: Joerg Bornemann <joerg.bornemann@theqtcompany.com>
This commit is contained in:
@@ -248,6 +248,7 @@ void QmlProfilerStatisticsView::clear()
|
|||||||
d->m_eventTree->clear();
|
d->m_eventTree->clear();
|
||||||
d->m_eventChildren->clear();
|
d->m_eventChildren->clear();
|
||||||
d->m_eventParents->clear();
|
d->m_eventParents->clear();
|
||||||
|
d->rangeStart = d->rangeEnd = -1;
|
||||||
}
|
}
|
||||||
|
|
||||||
void QmlProfilerStatisticsView::restrictToRange(qint64 rangeStart, qint64 rangeEnd)
|
void QmlProfilerStatisticsView::restrictToRange(qint64 rangeStart, qint64 rangeEnd)
|
||||||
|
|||||||
@@ -69,6 +69,7 @@ FlameGraphView::FlameGraphView(QWidget *parent, QmlProfiler::QmlProfilerModelMan
|
|||||||
|
|
||||||
void FlameGraphView::clear()
|
void FlameGraphView::clear()
|
||||||
{
|
{
|
||||||
|
m_isRestrictedToRange = false;
|
||||||
}
|
}
|
||||||
|
|
||||||
void FlameGraphView::restrictToRange(qint64 rangeStart, qint64 rangeEnd)
|
void FlameGraphView::restrictToRange(qint64 rangeStart, qint64 rangeEnd)
|
||||||
|
|||||||
Reference in New Issue
Block a user