diff options
| author | Ulf Hermann <ulf.hermann@qt.io> | 2018-05-11 17:12:17 +0200 |
|---|---|---|
| committer | Ulf Hermann <ulf.hermann@qt.io> | 2018-05-11 15:41:45 +0000 |
| commit | 9685711cb399682523d4ef28bcfdc067aebd9fde (patch) | |
| tree | 4efb0aedc09f56e063a7fdf072e464499e917e01 /src/plugins/qmlprofiler/memoryusagemodel.cpp | |
| parent | 3ce528d6aff9ea1d26c13fd0662c500eada430a1 (diff) | |
QmlProfiler: Remove accepted() methods
The only place where we used them was handlesTypeId(), and there it was
wrong. Each QmlProfilerTimelineModel has exactly one main feature it
subscribes to. It might additionally accept events of some auxiliary
features for context, but it doesn't really "handle" the respective
types in the sense that you could, for example, attach notes to them.
Therefore, just checking for the main feature is the right thing to do.
Change-Id: If0c00444084b957f3b99d3456cdbf703ae4afc3d
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
Diffstat (limited to 'src/plugins/qmlprofiler/memoryusagemodel.cpp')
| -rw-r--r-- | src/plugins/qmlprofiler/memoryusagemodel.cpp | 6 |
1 files changed, 0 insertions, 6 deletions
diff --git a/src/plugins/qmlprofiler/memoryusagemodel.cpp b/src/plugins/qmlprofiler/memoryusagemodel.cpp index 9fcaaa4cb38..a9a09185f54 100644 --- a/src/plugins/qmlprofiler/memoryusagemodel.cpp +++ b/src/plugins/qmlprofiler/memoryusagemodel.cpp @@ -141,12 +141,6 @@ QVariantMap MemoryUsageModel::details(int index) const return result; } -bool MemoryUsageModel::accepted(const QmlEventType &type) const -{ - return QmlProfilerTimelineModel::accepted(type) - || (type.rangeType() != MaximumRangeType && type.rangeType() != Compiling); -} - void MemoryUsageModel::loadEvent(const QmlEvent &event, const QmlEventType &type) { if (type.message() != MemoryAllocation) { |