aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGravatar Berthold Stoeger <bstoeger@mail.tuwien.ac.at>2021-01-26 20:40:22 +0100
committerGravatar Dirk Hohndel <dirk@hohndel.org>2021-04-02 13:53:23 -0700
commit36f0ba9abed595885edf52c8db848da71fa30b11 (patch)
tree0d0add67d6f193b05372f6b3c60a646461c3f467
parent752724aa1e077ba491a7e4f687e6a1d9b787b61d (diff)
downloadsubsurface-36f0ba9abed595885edf52c8db848da71fa30b11.tar.gz
profile: don't check for stepping past maximum time / depth
When moving a planner point with the cursor, nothing is wrong with extending the dive time by stepping beyond the current maximum. Same for depth. Signed-off-by: Berthold Stoeger <bstoeger@mail.tuwien.ac.at>
-rw-r--r--profile-widget/profilewidget2.cpp4
1 files changed, 0 insertions, 4 deletions
diff --git a/profile-widget/profilewidget2.cpp b/profile-widget/profilewidget2.cpp
index 7b6fb9b65..7113894a3 100644
--- a/profile-widget/profilewidget2.cpp
+++ b/profile-widget/profilewidget2.cpp
@@ -1829,8 +1829,6 @@ void ProfileWidget2::keyDownAction()
if (DiveHandler *handler = qgraphicsitem_cast<DiveHandler *>(i)) {
int row = handleIndex(handler);
divedatapoint dp = plannerModel->at(row);
- if (dp.depth.mm >= profileYAxis->maximum())
- continue;
dp.depth.mm += M_OR_FT(1, 5);
plannerModel->editStop(row, dp);
@@ -1894,8 +1892,6 @@ void ProfileWidget2::keyRightAction()
if (DiveHandler *handler = qgraphicsitem_cast<DiveHandler *>(i)) {
int row = handleIndex(handler);
divedatapoint dp = plannerModel->at(row);
- if (dp.time / 60.0 >= timeAxis->maximum())
- continue;
dp.time += 60;
plannerModel->editStop(row, dp);