mifr/subsurface
1
0
Fork 0
mirror of https://github.com/subsurface/subsurface.git synced 2025-02-17 20:36:15 +00:00
Code Issues Projects Releases Packages Wiki Activity
subsurface/CHANGELOG.md

20 lines
1,016 B
Markdown
Raw Normal View History

Fix invalid bailout gas choice when planning a CCR dive. Fixes a bug reported in https://groups.google.com/g/subsurface-divelog/c/8N3cTz2Zv5E: When planning a CCR dive with OC bailout, the diluent gas may be chosen as the first OC bailout gas, despite being set up with a use type of 'diluent', and likely not being available for open circuit breathing. `best_first_ascend_cylinder` is now initialised to an invalid value (instead of the first cylinder, which may or may not be a diluent cylinder), and its subsequent use is guarded by a validity check. Signed-off-by: Michael Keller <github@ike.ch>
2023-02-16 15:53:17 +13:00
desktop: fix bug in bailout gas selection for CCR dives
desktop: fix multi-dive editing of cylinders 3629a87 changed the handling of cylinders in multi-dives edit. Not only should the cylinders be the "same", but also at the same position. The code did not check whether the edited dives even had that many cylinders, leading to a null-pointer dereference. Check whether the cylinder exists before comparing it. Fixes #3578. Signed-off-by: Berthold Stoeger <bstoeger@mail.tuwien.ac.at>
2023-02-10 19:00:49 +01:00
desktop: fix crash on cylinder update of multiple dives
Cylindermodel: Improve editing of tank use Use the drop down for editing the tank use in the gas list in both the equipment tab and the dive planner. The tank use column is now available in the equipment tab for all dives and not just CCR dives, as 'not used' is a valid entry in both cases. However, if the current dive is an OC dive, only 'OC-gas' and 'not used' are shown. There still seems to be a problem that in some cases, when opening the planner after selecting an existing CCR dive the drop down in the planner does not list CCR gas uses - for some reason `displayed_dive` does not seem to be updated correctly on opening of the planner. But I have not been able to reproduce this consistently, and changing 'Dive mode' fixes this. Signed-off-by: Michael Keller <github@ike.ch>
2023-01-21 13:09:44 +13:00
desktop: use dynamic tank use drop down in equipment tab and planner
Desktop: Fix brightness configuration for OSTC4 The Heinrichs Weikamp OSTC4 introduced an additional 'Cave' brightness level that is dimmer than all existing ones. Signed-off-by: Michael Keller <github@ike.ch>
2022-12-25 12:10:13 +13:00
desktop: fix brightness configuration for OSTC4
Improvement: Show gases as diluent by default for CCR dives. Instead of adding all gases read from a dive computer as part of a dive log as 'OC-gas', add gases as 'diluent' if the dive has a dive mode of 'CCR'. This creates consistency with the ppO2 for CCR dives being tracked as sensor readings or a fixed setpoint, and not as the ppO2 of the current gas ad depth. A follow up question from this is whether gas use in the cylinders list on the Equipment tab should be user editable. This seems to be inconsistent at the moment, with gas constituent percentages downloaded from the dive computer being editable, but gas use not. Signed-off-by: Michael Keller <github@ike.ch>
2023-01-20 13:41:06 +13:00
equipment: Use 'diluent' as default gas use type if the dive mode is 'CCR'
Update CHANGELOG.md Signed-off-by: Martin Splitt <martinsplitt@google.com> Signed-off-by: Martin Splitt <splitti@google.com> Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2023-01-05 08:56:03 +01:00
htmlexport: fix search in HTML export
html export: update CHANGELOG.md Signed-off-by: Kim Delmar <62100831+KimDelmar@users.noreply.github.com>
2023-02-05 22:38:16 +11:00
htmlexport: fix diveguide display
statistics: fix zero-range on value axis The code that calculates the bounds of the value axis was broken when all items had the same value. In that case, increase the shown range explicitly. It doesn't really matter how much the range is increased, because all items will be at the center of the graph. Also, don't overwrite the "decimal" value of the class. That was just weird. Fixes #3544. Signed-off-by: Berthold Stoeger <bstoeger@mail.tuwien.ac.at>
2022-11-16 17:24:06 +01:00
statistics: fix value axis for degenerate value ranges
Show correct gas density in CCR mode When collecting the data for the infobox, we have already computed the current partial pressures of the breathing gas taking into accoutn the divemode. Use those rather than fractions (which for CCR mode are those of diluent) to compute the gas density. Reported-by: Pietro Tranquillini <p.tranquillini@gmail.com> Signed-off-by: Robert C. Helling <helling@atdotde.de>
2022-10-28 22:17:35 +02:00
profile: Show correct gas density when in CCR mode
statistics: add enough entries for date axis We must add one more entries than there are days, because the entries describe the values between histograms. The root cause of the problem here is that a histogram axis is misused for a continuous day-axis. Signed-off-by: Berthold Stoeger <bstoeger@mail.tuwien.ac.at>
2022-10-19 22:17:56 +02:00
statistics: show correct color of selected scatter items when switching to unbinned mode
statistics: fix display of month number in continuous date axis
statistics: fix range of continuous date axis
desktop: make time shift dialog show correct times This got broken in commit 7417f865cd ("cleanup: un-singletonize ShiftTimesDialog") and no one ever noticed. We need to intitialize the when variable and set up the initial texts in order for the time shift dialog to show the correct information. Doing this in the ButtonClicked member (right before the dialog is destroyed) makes absolutely no sense. Fixes #3535 Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2022-10-17 10:20:35 -07:00
desktop: fix dive time display in time shift dialog
update libdc garmin: relax string parsing sanity checks Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2023-01-02 17:00:48 -08:00
libdivecomputer: garmin: relax string parsing sanity checks
update libdivecomputer Garmin: decode dive mode Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2022-05-30 13:08:01 -07:00
CHANGELOG.md: fix bad markdown formatting The # and <> characters introduced formatting issues, for those who wanted to view our changelog in the Github repository. Signed-off-by: Lubomir I. Ivanov <neolit123@gmail.com>
2018-07-08 19:57:16 +03:00
---
* Always add new entries at the very top of this file above other existing entries and this note.
* Use this layout for new entries: `[Area]: [Details about the change] [reference thread / issue]`
CHANGELOG update This remove the old pre-3.0 entries and adds entries for 3.0.0->master Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2020-03-29 20:59:16 -07:00
# vim: textwidth=100
Reference in a new issue Copy permalink