torvalds at linux-foundation.org
Thu Jul 25 09:28:22 PDT 2013
On Thu, Jul 25, 2013 at 5:21 AM, Lars Bumiller <lars.bumiller at gmail.com> wrote:
> this is my first post and I hope this is the right way to do this, so sorry
> if not.
> I just had a problem occurred:
> I had previously 27 dives in Subsurface. When I downloaded another 4 (from
> an OSTC) all of those got the number '0'. I had the wrong time and date
> (year 2001(!)) for 2 of those dives, so that might have caused the problem.
> They get sorted in the right spot on top of the other 27 dives but they just
> all have the number '0'. I haven't tried re-downloading all dives yet to see
> if that might solve the problem.
So subsurface does *not* want to renumber existing dives unless you
tell it to explicitly - the reason being that some people might want
to log events that look like dives but aren't (ie pool sessions etc
for equipment testing, whatever), and they don't want those to have
numbers. Or alternatively, for the reverse reason: you may be missing
dives that you haven't logged, and you want your numbers to still
reflect (at least roughly) the actual dive number.
But that also automatically means that subsurface will not give dive
numbers to newly dives *unless* those new dives were all later than
the latest dive, *and* the last dive had a dive number.
So yes, if you download dives that aren't contiguous and all strictly
newer than the dives you already had, subsurface will leave them
unnumbered (which shows as "0" in some places, and doesn't show a
number at all in others - we should probably make that more
consistently be "no number shown").
And because subsurface will never renumber existing dives unless you
tell it to, that situation will remain, even if you try to
The solution is to tell it to renumber. In the "Log" menu there's a
"Renumber" thing, which will tell subsurface to renumber all dives
sequentially (starting from some dive number).
More information about the subsurface