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

9 lines
588 B
Markdown
Raw Normal View History

core: work around water temperature bug in Tecdiving DiveComputer.eu It appears to send a first sample with a water temperature of 0 C. If the next sample contains a more likely water temperature, overwrite the first one. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2022-04-13 08:51:48 -10:00
- core: work around bug in TecDiving dive computer reporting spurious 0 deg C water temperature in first sample
libdc integration: correctly parse DC_FIELD_SALINITY response libdivecomputer tries to be super careful in what it tells us. It only offers a density value if that is something that the dive computer explicitly supports, otherwise it just offers back a flag. We need to then update the density value ourselves. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2022-04-12 15:28:13 -10:00
- core: correctly parse DC_FIELD_SALINITY response; fixes incorrect water type with some dive computers, including the Mares Smart
Allow more than one media file when importing from the web To import media files from the web, increas the size of the dialog box and allow several URLs separated by newlines. Signed-off-by: Robert C. Helling <helling@atdotde.de>
2022-03-31 22:39:47 +02:00
- Desktop: Allow more than one media file to be imported from web
undo: Clear undo stack on file close The undo stack is only relevant to the dives that were loaded at the time the command was executed. If a file is closed, by specifically closing it or opening another file, then the undo commands will reference dives that aren't available anymore. Clearing the undo stack ensures that we don't crash or accidentally do some undefined modifications to the currently open file. Signed-off-by: Michael Andreen <michael@andreen.dev>
2022-04-02 17:39:38 +02:00
- undo: Clear undo stack when the current file is closed
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