diff options
| author |  Dirk Hohndel <dirk@hohndel.org> | 2014-06-09 20:32:44 -0700 |
|---|---|---|
| committer | Dirk Hohndel <dirk@hohndel.org> | 2014-06-09 20:32:44 -0700 |
| commit | 01026046451ef706bb184fad01032bb4c11add35 (patch) | |
| tree | 1a48dd77f2e9536f89a3747833980b9d0a660bec /qt-ui | |
| parent | 32e89123a296aba39ae50e10b141dc4b4820acc4 (diff) | |
| download | subsurface-01026046451ef706bb184fad01032bb4c11add35.tar.gz | |
Don't show the average depth for the selected dives
Being shown between the deepest and shallowest dive's max depth it
confuses a lot of people - the average depth is frequently less than the
shallowest of the dives, so at first glance it looks like the "average" is
less than the "minimum". So having three numbers grouped like this that
use different algorithms is just distracting.
Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
Diffstat (limited to 'qt-ui')
| -rw-r--r-- | qt-ui/maintab.cpp | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/qt-ui/maintab.cpp b/qt-ui/maintab.cpp index c0fdeca6e..19b47c872 100644 --- a/qt-ui/maintab.cpp +++ b/qt-ui/maintab.cpp @@ -505,7 +505,9 @@ void MainTab::updateDiveInfo(int dive) ui.salinityText->clear(); ui.depthLimits->setMaximum(get_depth_string(stats_selection.max_depth, true)); ui.depthLimits->setMinimum(get_depth_string(stats_selection.min_depth, true)); - ui.depthLimits->setAverage(get_depth_string(stats_selection.avg_depth, true)); + // the overall average depth is really confusing when listed between the + // deepest and shallowest dive - let's just not set it + // ui.depthLimits->setAverage(get_depth_string(stats_selection.avg_depth, true)); ui.depthLimits->overrideMaxToolTipText(QObject::tr("Deepest Dive")); ui.depthLimits->overrideMinToolTipText(QObject::tr("Shallowest Dive")); ui.sacLimits->setMaximum(get_volume_string(stats_selection.max_sac, true).append(tr("/min"))); |