diff options
| author | Shawn Rutledge <shawn.rutledge@qt.io> | 2016-06-09 08:55:09 +0200 |
|---|---|---|
| committer | Shawn Rutledge <shawn.rutledge@qt.io> | 2016-06-10 07:35:20 +0000 |
| commit | cf744b55a3fe252b8284956d18d61f46467dd721 (patch) | |
| tree | b23dd0f8e08b885abb60bd8cfcb7581353c8aacd /imports | |
| parent | 2870aaa09b86080941d7f44aa8910c73f6ce99c2 (diff) | |
QmlMessageTrace: detect and combine repeated sections of backtraces
If there are multiple tracepoints, it happens quite often that the
most recent backtrace contains the backtrace that we already captured
in handling the previous tracepoint. If the time difference is small
enough and we find such a duplicated sequence of methods, don't repeat
the Message output in the trace QML: pick up where the previous trace
left off.
Change-Id: I32f47430ab44fd7570569e0f347784d23197a3bc
Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
Diffstat (limited to 'imports')
| -rw-r--r-- | imports/Diagrams/UmlSequence/Message.qml | 9 |
1 files changed, 5 insertions, 4 deletions
diff --git a/imports/Diagrams/UmlSequence/Message.qml b/imports/Diagrams/UmlSequence/Message.qml index 92b441f..5b0ca94 100644 --- a/imports/Diagrams/UmlSequence/Message.qml +++ b/imports/Diagrams/UmlSequence/Message.qml @@ -47,13 +47,14 @@ MouseArea { property string params property string fromMethod property string backtrace + property bool inferredFromBacktrace: false + property bool toSelf: from && from === to + property bool backwards: from && to ? from.x > to.x : false + property real timestamp: 0 width: 100 height: 30 hoverEnabled: true z: 1 - property bool toSelf: from && from === to - property bool backwards: from && to ? from.x > to.x : false - property real timestamp: 0 Text { x: -root.x text: root.timestamp @@ -77,7 +78,7 @@ MouseArea { } Text { id: methodLabel - font.bold: true + font.bold: !root.inferredFromBacktrace anchors.horizontalCenter: parent.horizontalCenter anchors.verticalCenter: parent.verticalCenter } |