forked from qt-creator/qt-creator
QmlProfiler: Use bindings instead of JS methods for RangeMover
It's more intuitive to use and more QML-like. Change-Id: Ifbd05df59d8afaeb62acc9a6f1f3d4786f822169 Reviewed-by: Kai Koehne <kai.koehne@digia.com>
This commit is contained in:
@@ -376,8 +376,8 @@ Rectangle {
|
||||
}
|
||||
|
||||
// hack to pass mouse events to the other mousearea if enabled
|
||||
startDragArea: selectionRange.ready ? selectionRange.getLeft() : -x
|
||||
endDragArea: selectionRange.ready ? selectionRange.getRight() : -x - 1
|
||||
startDragArea: selectionRange.ready ? selectionRange.rangeLeft : -x
|
||||
endDragArea: selectionRange.ready ? selectionRange.rangeRight : -x - 1
|
||||
}
|
||||
MouseArea {
|
||||
id: selectionRangeControl
|
||||
@@ -419,7 +419,7 @@ Rectangle {
|
||||
startTime: selectionRange.startTimeString
|
||||
duration: selectionRange.durationString
|
||||
endTime: selectionRange.endTimeString
|
||||
showDuration: selectionRange.getWidth() > 1
|
||||
showDuration: selectionRange.rangeWidth > 1
|
||||
}
|
||||
|
||||
RangeDetails {
|
||||
|
||||
Reference in New Issue
Block a user