mifr/subsurface
1
0
Fork 0
mirror of https://github.com/subsurface/subsurface.git synced 2025-02-01 12:53:23 +00:00
Code Issues Projects Releases Packages Wiki Activity
subsurface/CHANGELOG.md

20 lines
1.1 KiB
Markdown
Raw Normal View History

Planner: Properly initialize salinity When the dive has no explicity salinity, our conversion between pressure and depth assumed salt water. Make this explicity by using the corresponding macro. When the planner starts and no salinity is set explicity, set the water type chooser to salt water to reflect our default assumption. Signed-off-by: Robert C. Helling <helling@atdotde.de>
2020-09-02 11:10:51 +02:00
planner: properly initialize salinity
Add an "Edit Gas Change" right-click option. This new option allows a user to select a new destination tank for an existing "Gas Change" event. This is useful when Subsurface's heuristics get tanks wrong after an import from a divecomputer. The use-case arose from sidemount divers with air-integrated transmitters as well as carrying a deco tank. Signed-off-by: Michael Werle <micha@michaelwerle.com>
2020-08-25 05:37:08 +09:00
desktop: add an "Edit Gas Change" right-click option [#2910]
Add CHANGELOG Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2020-08-21 16:13:56 -07:00
core: add support for Shearwater Peregrine (requires firmware V79 or newer)
core: fix dive renumbering logic on import 0249e12 split up the dive import logic in multiple steps. Thereby, the one of the conditions for renumbering the imported dives (is the last old dive numbered) got messed up: The first number of the new dive was compared to the total number of old dives, which makes no sense. - Simply check for the number of the last existing dive (if any). - Don't remember the number of old dives - the original table is not modified anyway. Fixes #2731 Signed-off-by: Berthold Stoeger <bstoeger@mail.tuwien.ac.at>
2020-08-17 20:59:46 +02:00
core: fix renumbering of imported dives [#2731]
Update CHANGELOG Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2020-08-15 13:52:54 -07:00
mobile: fix editing tank information
Planner: handle zero length segments when replanning When setting up a dive for replanning, we ignored zero length segments as those tend to be generated by gas changes. But it is possible to enter those in the planner and the replanning should not ignore those. So be more clever about gas changes. Let's add 10 seconds so we are not at two depths at the same time and help since add_stop also does not like zero length segments (it thinks we are trying to replace a waypoint). Fixes #2901 Signed-off-by: Robert C. Helling <helling@atdotde.de> Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2020-08-17 22:04:53 +02:00
planner: Handle zero length segments gracefully when replanning
Improve resolution of profile export The way we export the profile image (as direct export but also used for printing) is that we render the profile from the screen to a Pixmap and save that to a file. Unfortunately this results in very bad resultion and a blurred image. This is an attempt to improve that situation but it's still far from perfect: Rather than a QPixmap and grab, I now use a QImage (where I can set the size) and render, and indeed the picture resolution (when vied at fixed size) get's better this way. The disadvantage is that icons get smaller at the same rate und so there is a natural limit on how big we can get. Maybe somebody with better Qt knowledge can take off from here. In my opinion this is already a step in the right direction. Signed-off-by: Robert C. Helling <helling@atdotde.de> Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2020-08-07 11:43:49 +02:00
profile: improve resolution in printing and export
update CHANGELOG Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2020-07-14 10:26:58 -07:00
mobile: disable download button if no connection is selected
mobile: fix incorrect time stamps on GPS track points created via location service
core: correctly recognize A1 as BLE dive computer
Make MND display depend on O2 narcotic preference A while ago, we introduced a preference whether O2 should be considered narcotic. We used this when computing best mix or when entering the He content via MND. But we forgot to make the displayed MND depend on this preference. This patch add this. Fixes #2895 Signed-off-by: Robert C. Helling <helling@atdotde.de>
2020-07-11 13:15:21 +02:00
planner: Honor the "O2 narcotic" preference when computing MND
Fix dive merging with multiple cylinders We did something really horribly wrong when merging cylinders. It's been broken since commit 7c9f46a ("Core: remove MAX_CYLINDERS restriction"), and used some really strange logic. This rewrites the logic to be (I think) a bit more easy to understand. Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2020-06-28 14:26:26 -07:00
desktop: fix broken merging of dives with multiple cylinders
Update CHANGELOG Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2020-06-13 13:59:26 -07:00
mobile: add information about the cloud sync state to the Subsurface plate in the menu
Implement Seac SeacSync databaser parser. Dives for the seac action computer are imported by the seacsync program into two tables in an sqlite3 database. The dive information is read from the headers_dive table. The dive_data table is then queried for each dive to get samples. The seac action computer is the only current supported computer by the seacsync program. It only supports two gas mixes, so the parser will toggle between two cylinders whenever it detects a change in the active O2 mix. Dive start time is stored in UTC with a timezone offset. A helper function to read this was added to qthelper. Default cases have been added to some switch statements to assist in future development for other dive types and salinity. Example database has been added to ./dives/TestDiveSeacSync.db Signed-off-by: James Wobser <james.wobser@gmail.com>
2020-07-16 21:40:46 -04:00
core: Add parser for SeacSync db. Currently only Seac Action uses SeacSync program.
ReleaseNotes for 4.9.4 Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2020-05-01 12:09:38 -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