Like that we can drop the deferred setting of model manager and we can
announce the features right away on construction.
Change-Id: I8b4eb3e94046511b0e637084768e919649115e77
Reviewed-by: Kai Koehne <kai.koehne@theqtcompany.com>
We can easily implement all needed functionality with only the public
interface.
Change-Id: Ibf22f2e4bc27a8b506f0164e0e1fdf529b1a9e45
Reviewed-by: Kai Koehne <kai.koehne@theqtcompany.com>
It seems those were forgotten when the scene graph profiler was
refactored.
Change-Id: I4cf5f1cae701ec4ff64659bd023fb5941715e7e1
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
It shouldn't display 0-size timings and it should distinguish the
threads more clearly. Also, we display the gross render time in
addition to the render time breakdown. This seems to be rather
important information for users.
Change-Id: I3c1d94f1489902a815c20831e8e1059c815ef129
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
This helps if you have multiple pixmaps with equal names.
Change-Id: I39a16f55d16c5729483c037b8c125795105fae0a
Reviewed-by: Alessandro Portale <alessandro.portale@digia.com>
Also add a stub input events model to represent that feature.
Change-Id: Idd05b9452b7c6920779e72966ce62c0a1decaeef
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
It means the same but is shorter and doesn't get elided.
Change-Id: I0ef221bb844691b9c15a3c10743bfd7389fe95ae
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
The scene graph profiler was pretty barren. The ranges it showed were
only vaguely related to actual events and the numbers shown in the
labels weren't really informative.
This change shows every stage in GUI thread and rendering thread as its
own range, so that you can easily see now if a particular stage takes
unusually long. This comes at a cost, though: The color is used for
showing event types instead of frame rates now and there is no 1:1
mapping of rows to threads anymore. The first row is still reserved
for the GUI thread and the second one for the render thread. Further
rows are used as needed, though, and you can meaningfully expand the
category now.
Task-number: QTBUG-39876
Change-Id: Ib91ba454dd0e3e7482ca2afe6d3c80d9868bcce3
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
Adapt to the new signature of the details method and don't create
unnecessary nested maps.
Change-Id: Iab8d31e48d35923fee3e258c0390459a81ece746
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
The memory profiler aggregates allocations originating from the same
QML/JS constructs into one event. This change makes sure the origins
are really the same calls, not only the same functions and gives some
more details on hom much memory was allocated or deallocated in how
many steps.
Change-Id: I784c521855122f7b3b894417de0afb216766e2d4
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
The indices SortedTimelineModel returns are only valid until you insert
something at a different place than the end. If you do that, all later
events are shifted by one. We can "fix" that by also shifting the saved
indices.
Change-Id: I63180dabea0c52db55e799b023b3f2bf84f9e59a
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
lastTimeMark is just the end of the last recorded event. The memory
will still be allocated after that.
Change-Id: Ica12993d7b1572c145bba6373461240a5e846fa9
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
By showing the same numbers with units in the labels we avoid leading
people to assume bytes as unit.
Change-Id: I56d2ca5f21434fd24a305aebd434371438da7ebb
Reviewed-by: Kai Koehne <kai.koehne@digia.com>
