<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 22/01/2017 00:16, Robert Helling
wrote:<br>
</div>
<blockquote
cite="mid:AEE2762C-1A0A-4F06-9A14-49229F75892A@atdotde.de"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
Willem,
<div class=""><br class="">
<div>
<blockquote type="cite" class="">
<div class="">On 20 Jan 2017, at 07:42, Willem Ferguson <<a
moz-do-not-send="true"
href="mailto:willemferguson@zoology.up.ac.za" class=""><a class="moz-txt-link-abbreviated" href="mailto:willemferguson@zoology.up.ac.za">willemferguson@zoology.up.ac.za</a></a>>
wrote:</div>
<br class="Apple-interchange-newline">
<div class=""><span style="font-family: Helvetica;
font-size: 12px; font-style: normal; font-variant-caps:
normal; font-weight: normal; letter-spacing: normal;
orphans: auto; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal; widows: auto;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
float: none; display: inline !important;" class="">4) I
could not replicate it in this specific exercise, but in
some cases when re-opening a dive for editing in the
planner, the part of the dive where the planner
initially calculated the deco profile, (upon re-editing)
comes up as hard depth/time milestones (i.e. fixed and
indicated by small white circles as if they were forced
(explicitly specified in the Dive Planner Points table)
all the way to the surface during the initial planning.</span></div>
</blockquote>
</div>
<br class="">
</div>
<div class="">this is the easy part to answer: The information
about which points were entered by the user and which are
computed is not saved to the file system. So you get this when
you load the dive from a file. The others I have no idea about.
Will look at those when I have a little bit of time on my hands.
Do you have an xml file of the dive for me so I can have a look
at the xml and see how it behaves in the planner?</div>
<div class=""><br class="">
</div>
<div class="">Best</div>
<div class="">Robert</div>
</blockquote>
<p>Hi Robert,</p>
<p>Attached a dive log with several dive plans. These plans were
made for a cave system with a cave entrance at 15-16 m. The whole
dive is "hard-coded" with dive planner points to the deepest part
of the dive and back to the entrance, so the only deco
calculations that the planner does is from the cave entrance back
to the surface. I hope this is use-able?</p>
<p>I think the priority is to discover how the zero-points get
inserted into the plan because this actually creates an erroneous
plan. It appears like this happens during recreating the plan from
XML, not upon writing the plan to XML. After that it would be very
useful if the last dive planner point could be remembered so that,
when-re-edited, the planned part of the dive plan shows up
correctly.</p>
<p>If there is anything you would like me to do, shout.</p>
<p>Kind regards,</p>
<p>willem</p>
<p><br>
</p>
</body>
</html>