[PATCH] Correctly determine pre-saturation

[Robert Helling]

Rick,

> Am 10.06.2016 um 01:12 schrieb Rick Walsh <rickmwalsh at gmail.com>:
> 
> Where I'm really struggling is that I haven't come up with a case where I can see any effect.  Can you outline an example test case?

my test case was: First start with an empty log and plan a reference dive (I was using 30min at 60m with air) and write down the runtime.

Then load your regular log and find a dive (which must not be the latest as that has always been my test case before, take one significantly back in time) with significant deco and then plan again the reference dive but date it back so that it starts shortly after the end of that dive. The runtime should be much longer and it should change when you move the start time of the planned dive by an hour say.

Best
Robert
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.subsurface-divelog.org/pipermail/subsurface/attachments/20160610/472dd35d/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 496 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.subsurface-divelog.org/pipermail/subsurface/attachments/20160610/472dd35d/attachment.sig>