If a merge mishap creates inconsistent data for a dive in git storage, where the dive references a dive site that no longer exists, the app would crash when trying to open the cloud storage. I don't think a NULL dive could ever happen, but this seems fairly cheap insurance. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
13 lines
690 B
Markdown
13 lines
690 B
Markdown
- core: avoid crash with corrupted cloud storage
|
|
- planner: make ESC (cancel plan) work when moving handles
|
|
- dive list: make dive guide visible in dive list [#3382]
|
|
- general: rename dive master to dive guide
|
|
- desktop: Don't lose cursor position in notes when switching between windows [#3369]
|
|
- Uemis support: fix the ability disconnect/reconnect the Zurich when its filesystem is full
|
|
- libdivecomputer: add support for latest BLE hardware in OSTC dive computers
|
|
|
|
---
|
|
* 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]`
|
|
# vim: textwidth=100
|