mirror of
https://github.com/subsurface/subsurface.git
synced 2025-01-19 22:35:27 +00:00
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>
This commit is contained in:
parent
32e89123a2
commit
0102604645
1 changed files with 3 additions and 1 deletions
|
@ -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")));
|
||||
|
|
Loading…
Add table
Reference in a new issue