<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Willem,<div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 20 Jan 2017, at 07:42, Willem Ferguson <<a href="mailto:willemferguson@zoology.up.ac.za" class="">willemferguson@zoology.up.ac.za</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></body></html>