diff options
author | Lubomir I. Ivanov <neolit123@gmail.com> | 2014-11-17 22:59:19 +0200 |
---|---|---|
committer | Dirk Hohndel <dirk@hohndel.org> | 2014-11-17 21:04:27 +0000 |
commit | 609036c57031073b6ae7e829c0473815297b8247 (patch) | |
tree | 71f8b531e73cf34d14897f81dfd9bfd0c232cc56 /devicedetails.cpp | |
parent | c688cc52e8c295ba1a77553457d97d598c3da51e (diff) | |
download | subsurface-609036c57031073b6ae7e829c0473815297b8247.tar.gz |
Ruler: fix weird behaviour near x = 0
RulerNodeItem2::recalculate() does something which is
apparently not a good idea in combination with
RulerNodeItem2::mouseMoveEvent().
Each time the mouse moves, setPos() is called. Then in
recalculate() the x() value is checked and if less than 0
it's changed to x = 0 (setPos(0, y());).
This last call (setPos(0, y());)
however does not work and the value remains less than zero
leaving one of the ruler points outside of the graph.
To solve the issue we add a silly explicit check if x() < 0
before calling setPos() in RulerNodeItem2::mouseMoveEvent().
The 'x() > timeAxis->posAtValue(data->sec)' strangely works
on the other hand.
Signed-off-by: Lubomir I. Ivanov <neolit123@gmail.com>
Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
Diffstat (limited to 'devicedetails.cpp')
0 files changed, 0 insertions, 0 deletions