forked from qt-creator/qt-creator
QmlProfiler: Remove detailed progress tracking
The progress bar in the state widget was rather meaningless. We rarely know how many events we expect and it's rather hard to tell how long each model will take to process them. Instead, we just show a 0-ranged progress bar to tell the user that "something is happening". Change-Id: Icb80840d1f0a1538bcf254faa37cbb36e25d342c Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
This commit is contained in:
@@ -79,30 +79,19 @@ void QmlProfilerRangeModel::loadData()
|
||||
// store starttime-based instance
|
||||
m_data.insert(insert(event.timestamp(), event.duration(), event.typeIndex()),
|
||||
QmlRangeEventStartInstance());
|
||||
updateProgress(count(), eventList.count() * 5);
|
||||
}
|
||||
|
||||
updateProgress(1, 5);
|
||||
|
||||
// compute range nesting
|
||||
computeNesting();
|
||||
|
||||
updateProgress(2, 5);
|
||||
|
||||
// compute nestingLevel - nonexpanded
|
||||
computeNestingContracted();
|
||||
|
||||
updateProgress(3, 5);
|
||||
|
||||
// compute nestingLevel - expanded
|
||||
computeExpandedLevels();
|
||||
|
||||
updateProgress(4, 5);
|
||||
|
||||
if (supportsBindingLoops())
|
||||
findBindingLoops();
|
||||
|
||||
updateProgress(1, 1);
|
||||
}
|
||||
|
||||
void QmlProfilerRangeModel::computeNestingContracted()
|
||||
|
||||
Reference in New Issue
Block a user