ae733fd8a8
The logbook ringbuffer is always updated sequentially. Therefore, emtpy entries can only be present after the oldest dive. However it appears that under some special conditions (for example an empty battery during the dive), the logbook entry is not always stored correctly, which can result in an empty entry after all. I suspect that at the start of each dive, the OSTC erases the next available entry in the logbook ringbuffer and updates the internal write pointer. Once the dive is finished, the actual content of the erased logbook is written. Thus, when the OSTC runs out of battery power during the dive, that last step never happens, and the erased entry remains in place. As a workaround, ignore all empty logbook entries instead of assuming we reached the last dive.
Overview ======== Libdivecomputer is a cross-platform and open source library for communication with dive computers from various manufacturers. The official web site is: http://www.libdivecomputer.org/ The sourceforge project page is: http://sourceforge.net/projects/libdivecomputer/ Installation ============ On UNIX-like systems (including Linux, Mac OS X, MinGW), use the autotools based build system. Run the following commands from the top directory (containing this file) to configure, build and install the library and utilities: $ ./configure $ make $ make install If you downloaded the libdivecomputer source code directly from the git source code repository, then you need to create the configure script as the first step: $ autoreconf --install To uninstall libdivecomputer again, run: $ make uninstall Support ======= Please send bug reports, feedback or questions to the mailing list: http://libdivecomputer.org/cgi-bin/mailman/listinfo/devel or contact me directly: jef@libdivecomputer.org License ======= Libdivecomputer is free software, released under the terms of the GNU Lesser General Public License (LGPL). You can find a copy of the license in the file COPYING.