Hello
Since I have compiled and installed 1.91 alpha with the new logbook, I can't import dive with jdivelog or diving log.
thanks
1.91 alpha (changeset 384) Solved
-
- Posts: 4469
- Joined: 13 May 2007, 18:07
Re: 1.91 alpha (changeset 384)
Correct.
When playing around with alpha versions, have look into the changelog: https://bitbucket.org/heinrichsweikamp/ ... ngelog.txt
CHANGE: Logbook format 21: store & shows dive model (sat/desat or GF_low/high factors),CNS profile, GF profile. WARNING: the upgrade is not reversible without loosing all your profiles.
a) alpha versions usually come with severe side-effects
b) we don't give much support for alpha versions
We'll expect Divinglog and JDivelog to support the new version soon. The 1.91beta won't be released until the support is available
Regards,
Matthias
When playing around with alpha versions, have look into the changelog: https://bitbucket.org/heinrichsweikamp/ ... ngelog.txt
CHANGE: Logbook format 21: store & shows dive model (sat/desat or GF_low/high factors),CNS profile, GF profile. WARNING: the upgrade is not reversible without loosing all your profiles.
a) alpha versions usually come with severe side-effects
b) we don't give much support for alpha versions
We'll expect Divinglog and JDivelog to support the new version soon. The 1.91beta won't be released until the support is available

Regards,
Matthias
Re: 1.91 alpha (changeset 384)
Thanks Matthias
No problem I'll wait for jdivelog or diving log support.
anyway the new logbook is a good improvement.
regards.
richard
No problem I'll wait for jdivelog or diving log support.
anyway the new logbook is a good improvement.
regards.
richard
OSTC 2N 2084
-
- Posts: 4469
- Joined: 13 May 2007, 18:07
Re: 1.91 alpha (changeset 384)
Hi,
make sure to backup your dives then (When the Divinglog/Jdivelog update is out) before installing the official 1.91beta to avoid data loss.
Cheers,
Matthias
make sure to backup your dives then (When the Divinglog/Jdivelog update is out) before installing the official 1.91beta to avoid data loss.
Cheers,
Matthias