forked from qt-creator/qt-creator
QmlProfiler: Refactor complete() methods
The complete() methods do something more specific. We should call them by what they do. Also, we don't need to signal the finishing of data acquisition via a signal and most of the postprocessing can happen in the worker thread. Change-Id: Iae986aefb8e7e7d4327c481d7a85325bbff7fa48 Reviewed-by: Joerg Bornemann <joerg.bornemann@theqtcompany.com>
This commit is contained in:
@@ -110,6 +110,9 @@ public:
|
||||
quint64 recordedFeatures() const;
|
||||
void setRecordedFeatures(quint64 features);
|
||||
|
||||
void acquiringDone();
|
||||
void processingDone();
|
||||
|
||||
static const char *featureName(QmlDebug::ProfileFeature feature);
|
||||
|
||||
signals:
|
||||
@@ -133,8 +136,6 @@ public slots:
|
||||
const QmlDebug::QmlEventLocation &location,
|
||||
qint64 ndata1, qint64 ndata2, qint64 ndata3, qint64 ndata4, qint64 ndata5);
|
||||
|
||||
void complete();
|
||||
|
||||
void save(const QString &filename);
|
||||
void load(const QString &filename);
|
||||
|
||||
|
||||
Reference in New Issue
Block a user