On 20.05.2014, at 09:09, Willem Ferguson <[email protected]> wrote:
Willem,
> An approach may be to have primitive events such as "connect" and
> "disconnect". An event that marks a cylinder change should then actually
> insert two events, possibly separated by a second in time, a disconnect and a
> connect.
just make sure, you don’t break backwards compatibility, i.e. the possibility
to read old log files. Plus the fact that we inherit the gas change events from
libdivecomputer (with their limit of only providing info about the gas rather
than the cylinder). Maybe we can have semantics that an old style “gas change”
event implies a disconnect of all previous cylinders and have special events
(“enable gas”) for the rebreather use you intend.
Best
Robert
--
.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oOo.oO
Robert C. Helling Elite Master Course Theoretical and Mathematical Physics
Scientific Coordinator
Ludwig Maximilians Universitaet Muenchen, Dept. Physik
Phone: +49 89 2180-4523 Theresienstr. 39, rm. B339
http://www.atdotde.de
Enhance your privacy, use cryptography! My PGP keys have fingerprints
A9D1 A01D 13A5 31FA 6515 BB44 0820 367C 36BC 0C1D and
DCED 37B6 251C 7861 270D 5613 95C7 9D32 9A8D 9B8F
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ subsurface mailing list [email protected] http://lists.hohndel.org/cgi-bin/mailman/listinfo/subsurface
