On Sun, Oct 15, 2017 at 01:57:23PM +0200, Jan Mulder wrote: > > I marked 351 as must fix for 4.7. That should have been dealt with a long > > time ago. The challenge is that it's non-trivial to do so. How do I tell > > the difference between "user wants to start with a new file and delete the > > dives in their repo" and "user accidentally clicked "new dive log and then > > save to ckoud". We could add a warning if all of the dives in the server > > side repo are deleted by a save... I'll have to think a bit more about > > this - but open to ideas from others as well! > > In "normal" use, a logbook is only growing in size/#dives, so we could issue > a warning when the #dives currently in the divelist is smaller than the > #dives in the cloud storage before an attempt to save. In this case, the > user who deliberately want to clean the cloud data, needs to ok this, but > that seems acceptable to me, as normally we are only adding dives (and > correcting existing dives).
I agree - that seems reasonable. Any volunteers to work on this, or should I add this to my backlog? /D _______________________________________________ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
