Allow replanning of logged dives
dbdavide at gmail.com
Tue May 12 02:30:18 PDT 2015
On Tue, May 12, 2015 at 10:56 AM, Robert C. Helling <helling at atdotde.de> wrote:
> I didn't go for your simpler approach as it is ambiguous: Given a real dive,
> at which point is the planner supposed to take over? The first time you
> violate the ceiling? Or the last? Imagine for example that you first violate
> the ceiling at 22m but then you stop at 21m an stay there longer than
> needed, e.g. until the ceiling drops to 12m. Then you proceed with your
> ascent and again at 5m go through the ceiling again and surface. Which is
> the information you would want to be displayed?
You are right
> Therefore, with my proposed solution, the decides at which waypoint the
> planner is supposed to take over by holding the control key and clicking the
> corresponding dustbin icon in the table (thereby deleting that and all
> following waypoints).
> If you simply want to know a time to surface at each point of the dive, we
> have been doing that for a long time: This can be turned on with one of the
> icons besides the profile and displays the TTS in the info box (I should
> say, however, that this can be a bit expensive in computation time, so the
> responsiveness of the user interface loses some snappiness).
I keep it disabled because with my dives I always get "Show/NDL/TTS
was disabled because of excessive processing time" (I'm on a I7 box).
Therefore I thought to something aimed only to deco violation.
Thank you for your clear explanation
More information about the subsurface