1.20.0

Suunto Nautic/Ocean: a dive cut short by a dropped Bluetooth link now carries on from where it stopped. Tested on DC Tester build 27 with real link drops on a Nautic (#29). Full details in CHANGELOG.md.

Added

• Suunto Nautic/Ocean: a dive whose download a dropped link (or a cancel) cut short carries on from the bytes already received on the next connection, instead of starting again from offset 0. The next download of that dive fetches its /Summary for the full size and reads only the missing part in pages from the first missing byte; if the watch won't serve the pages, the dive is streamed from the start in the same attempt. The result is still checked against the listed size. The Explorer, Auto download and retrieveDiveLogs all resume; up to 4 dives are kept per watch, in memory only (#102)
• SuuntoNauticResume holds the resume buffers (attached to every Nautic/Ocean device by openBLEDevice), and NauticSyncLink.resumableBytes(of:) reports how much of a dive is kept; Auto download logs "carrying on from byte N" (#102)

Fixed

• open_ble_device stops retrying dc_device_open once the link has dropped or a close waits (DC_STATUS_NODEVICE / DC_STATUS_CANCELLED), instead of failing again every 3 s on a dead link; a reconnect after a drop answers in seconds instead of about 18 s (#102)
• DC Tester: a failed Explorer download says to reconnect from the device list and how many bytes are kept to carry on from, instead of suggesting a force-quit and a Bluetooth toggle (#102)

In testing, two drops in one dive finished in under 4 minutes (about 10 on build 26), and the resumed data was byte-identical to a full download.

DC Tester: build 27.