QmlProfiler: Eliminate QmlProfilerDataState

This class is only accessible through the model manager and there is no
real point in keeping it separate.

Change-Id: I575d47c08aa8f6731d44739f9604072b95fd1dcd
Reviewed-by: Joerg Bornemann <joerg.bornemann@theqtcompany.com>
This commit is contained in:
Ulf Hermann
2015-09-10 13:51:54 +02:00
parent f373c6794e
commit ddb872727f
6 changed files with 70 additions and 108 deletions

View File

@@ -193,8 +193,8 @@ void QmlProfilerStateWidget::updateDisplay()
return;
}
QmlProfilerDataState::State state = d->m_modelManager->state();
if (state == QmlProfilerDataState::Done || state == QmlProfilerDataState::Empty) {
QmlProfilerModelManager::State state = d->m_modelManager->state();
if (state == QmlProfilerModelManager::Done || state == QmlProfilerModelManager::Empty) {
// After profiling, there is an empty trace
if (d->m_modelManager->traceTime()->duration() > 0 &&
(d->m_modelManager->isEmpty() || d->m_modelManager->progress() == 0)) {
@@ -208,7 +208,7 @@ void QmlProfilerStateWidget::updateDisplay()
else // Application died before all data could be read
showText(tr("Application stopped before loading all data"), true);
return;
} else if (state == QmlProfilerDataState::AcquiringData) {
} else if (state == QmlProfilerModelManager::AcquiringData) {
showText(tr("Waiting for data"));
return;
}