summaryrefslogtreecommitdiffstats
path: root/qt-models
diff options
context:
space:
mode:
authorGravatar Berthold Stoeger <bstoeger@mail.tuwien.ac.at>2019-03-28 17:23:35 +0100
committerGravatar Dirk Hohndel <dirk@hohndel.org>2019-04-12 18:19:07 +0300
commit4a3ffeba05fb90a1c9c29d939599bf770db5f0ce (patch)
tree8991d8049f0e57f95852755b797f28150feaf07e /qt-models
parent8287d86d2b83fb5a343f2638391b1393a73cde72 (diff)
downloadsubsurface-4a3ffeba05fb90a1c9c29d939599bf770db5f0ce.tar.gz
Undo: remove ADD mode from main tab
Instead of letting the user edit the fields before adding a dive, simply add an empty dive. Thus, the ADD mode of the main tab can be removed. Constructing a new dive with default-depth and making sure that the dive is displayed correctly is very subtle. This all needs to be detangled in due course. Signed-off-by: Berthold Stoeger <bstoeger@mail.tuwien.ac.at>
Diffstat (limited to 'qt-models')
-rw-r--r--qt-models/diveplannermodel.cpp4
1 files changed, 2 insertions, 2 deletions
diff --git a/qt-models/diveplannermodel.cpp b/qt-models/diveplannermodel.cpp
index 35146f9ef..2dfeff7eb 100644
--- a/qt-models/diveplannermodel.cpp
+++ b/qt-models/diveplannermodel.cpp
@@ -1145,11 +1145,11 @@ void DivePlannerPointsModel::createPlan(bool replanCopy)
if (!current_dive || displayed_dive.id != current_dive->id) {
// we were planning a new dive, not re-planning an existing one
displayed_dive.divetrip = nullptr; // Should not be necessary, just in case!
- Command::addDive(&displayed_dive, QString(), autogroup, true);
+ Command::addDive(&displayed_dive, autogroup, true);
} else if (replanCopy) {
// we were planning an old dive and save as a new dive
displayed_dive.id = dive_getUniqID(); // Things will break horribly if we create dives with the same id.
- Command::addDive(&displayed_dive, QString(), false, false);
+ Command::addDive(&displayed_dive, false, false);
} else {
// we were planning an old dive and rewrite the plan
mark_divelist_changed(true);