From c81ed0bf9c0cb2d7169399feb34661472eaab8b6 Mon Sep 17 00:00:00 2001
From: Ulf Hermann <ulf.hermann@qt.io>
Date: Thu, 2 Jun 2016 10:19:30 +0200
Subject: [PATCH] QmlProfiler: Send the correct end events when restricting to
 range

Clamping the timestamps and then sending the original events doesn't
make a lot of sense.

Change-Id: I42a42968d0188acb040649483d642c6b3f3e1038
Reviewed-by: Joerg Bornemann <joerg.bornemann@qt.io>
---
 src/plugins/qmlprofiler/qmlprofilerdatamodel.cpp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/plugins/qmlprofiler/qmlprofilerdatamodel.cpp b/src/plugins/qmlprofiler/qmlprofilerdatamodel.cpp
index e9ab29d169f..92e07bcc8c9 100644
--- a/src/plugins/qmlprofiler/qmlprofilerdatamodel.cpp
+++ b/src/plugins/qmlprofiler/qmlprofilerdatamodel.cpp
@@ -218,7 +218,7 @@ void QmlProfilerDataModel::replayEvents(qint64 rangeStart, qint64 rangeEnd,
                         if (stack.isEmpty()) {
                             QmlEvent endEvent(event);
                             endEvent.setTimestamp(rangeEnd);
-                            loader(event, d->eventTypes[event.typeIndex()]);
+                            loader(endEvent, d->eventTypes[event.typeIndex()]);
                         } else {
                             stack.pop();
                         }