PLanner and dive list suggestions

Dirk Hohndel dirk at hohndel.org
Mon Apr 22 11:47:39 PDT 2019


Please don't drop the mailing list in these conversations...

We have new code in master that allows you to split out dive computers into separate dives. That should allow you to do all you want to do.
Split out the incorrectly merged C1D1 C2D1, merge C2D1 & C2D2, then merge C1D1 with C2D(1+2).

/D

> On Apr 19, 2019, at 11:28 AM, David Wilkinson <DavidJ.wilkinson at outlook.com> wrote:
> 
> Dirk,
>  
> Thank you for the response and let me reiterate my appreciation of Subsurface. Let me try to Clarify.
>  
> Suggestion #1b
> When using 2 dive computers that record dives slightly differently and using the merge function to bring a number of dives together that are really 1 I would like to have the ability to control better the combination (The normal Merge when using 1 dive computer is great, but when using 2 seems to break down)
>  
> Dive Computer 1 (C1):
> Dive 1 (D1)
> 
>  
> Dive Computer 2 (C2):
> Dive 1 (D1)
> 
> Dive 2 (D2)
> 
>  
> The system automatically combines C1D1 with C2D1 because the times match (really cool functionality) and also links a dive plan to these if the time matches
> When I try to merge C2D2 with the now combined Dive it would be nice if it merged C2D1 and C2D2 because they are the same computer or give manual control of the merge within a combined dive set.
>  
> When I was careful on the upload order and loader C2 first and performed a merge before uploading C1 it then created a compound dive with 2 rather than 3 dives
>  
> Suggestion #1c
> I would like the ability to save the plan from a previously completed dive currently it appears that I need to edit the dive in the planner which gives me the plan and completed profile in the editor (I like this view) and then save as new, however this gives a copy of the entire plan+completed profile and I would like to separate the plan so that I can reuse it
>  
> Is really an extension of #1a providing the ability to extract a copy of a single dive from a compound dive.
> Compound Dive plan
> 
> Compound Dive Execution
> 
>  
> I would like to extract a copy of the plan for modification on another future dive
>  
> Suggestion #2
> >> Using Windows 10 I downloaded 4.8.6 to get the time/date change fix but found that the Bluetooth upload did not work and I had to revert to 4.8.5 (Minor issue)
>  
> >That's surprising as it uses the exact same software stack. Given that BLE download on Windows is fairly unreliable, could this just be a temporary issue? I.e., have you tried un-pairing and re-pairing the Shearwater?
>  
> I too suspect that this is a temporary issue although I did unpair and repair and restart all the devices. What surprised me was that as soon as I reverted to 4.8.5 it worked like a charm. I have not upgraded to 4,8,6 again yet although that will be my next test
>  
> Suggestion #3
> >> I have just started to use the mobile version on android along with the Windows desktop, both synchronized through the cloud storage (This worked perfectly), I would like to request that the dive list on Android behave similar to the dive list on the desktop. On android multiple profiles of the same dive appear separately in the list where as on the desktop they are behind a single dive number. I think my preference would be for them to appear similar to the desktop version although I would like the ability to explicitly manage each profile.
>  
> > I don't think that's the case - on Android we only show the first dive computer and completely ignore the additional dive computers. Are you sure that they are indeed shown as separate dives? If yes, I'd love to see a screencast video that shows that phenomenon because I don't understand how that could be happening.
>  
> I will try this again and let you know, I have done too much manual editing to explain the scenario with confidence and clear screen shots
>  
> Dave

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.subsurface-divelog.org/pipermail/subsurface/attachments/20190422/0be53f32/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 4BAF36647C7B4B3CB2EEB6FFEBC242AB.png
Type: image/png
Size: 22824 bytes
Desc: not available
URL: <http://lists.subsurface-divelog.org/pipermail/subsurface/attachments/20190422/0be53f32/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 376FD8409EDE48C3A5A5DC50545AA37E.png
Type: image/png
Size: 22596 bytes
Desc: not available
URL: <http://lists.subsurface-divelog.org/pipermail/subsurface/attachments/20190422/0be53f32/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 1FD685753D6148599B3154920CD23F7C.png
Type: image/png
Size: 6455 bytes
Desc: not available
URL: <http://lists.subsurface-divelog.org/pipermail/subsurface/attachments/20190422/0be53f32/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0724AF4451F04F1AABF3C6DACCAECBB6.png
Type: image/png
Size: 17212 bytes
Desc: not available
URL: <http://lists.subsurface-divelog.org/pipermail/subsurface/attachments/20190422/0be53f32/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0A8F063AD1F54E98A75B2CE7D677A5B1.png
Type: image/png
Size: 20517 bytes
Desc: not available
URL: <http://lists.subsurface-divelog.org/pipermail/subsurface/attachments/20190422/0be53f32/attachment-0009.png>


More information about the subsurface mailing list