bug in the 1.28 ??

[nicolas schreyer]

1?
last night, I putted the OSTC in simulation mode to show a friend what it looked like under water...

today, I deletedthis 1min dive from logbook...

since this it is the complete anarchy (again) in the logbook;
the dives I made in January-February are logged from #20...
the today's dive is logged on #1 but isn't downloadable (Divelog 4.0.10)

2?
as I plugged the interface the deco info were deleted too... (a few time remaining since today at noon..)

what it is going on ??

[heinrichsweikamp]

Hello Nicolas,

I've tested to delete some dives with the 1.29 (btw. please update to the 1.29, the 1.28 has bug and was recalled) and it worked fine. I admit there are still issues with the delete function, especially when you have half or broken dives in the memory (aborted simulations or dives less then one minute). When the current to-do list is getting shorter we'll rewrite the entire logbook handling.

regards,
Matthias

[wrobell]

heinrichsweikamp Wrote:
-------------------------------------------------------
> Hello Nicolas,
>
> I've tested to delete some dives with the 1.29
> (btw. please update to the 1.29, the 1.28 has bug
> and was recalled) and it worked fine. I admit
> there are still issues with the delete function,
> especially when you have half or broken dives in
> the memory (aborted simulations or dives less then
> one minute).

i can confirm, that there are quite consistent
problems with logbook like

- displaying wrong dives after deleting a dive
(going to main screen and to logbook again and
proper dives were displayed)

- dive being deleted even if removal process was
aborted (during countdown)

- even wrong dive being deleted (fixed in new version,
i believe)

- very slow (several minutes) dive logbook display
after deleting a dive (i had some few hours simulated
dives)

> When the current to-do list is
> getting shorter we'll rewrite the entire logbook
> handling.

is it possible to publish the to-do list on the
webpage? it would be nice to know what the future
is and what are currently acknowledged errors.

[heinrichsweikamp]

Hello,

While I can not confirm all of your errors above, the current list have (Without any order):
- Improve stand-alone simulator
- Replace mid-size font
- More features in Gauge and Apnoe mode
- Use other 50% of external memory for the logbook
- On-Time, Sleep-Time counter for more accurate battery sign
- Improve Onboard-Logbook functions
- 2nd Dive screen for the blind
- 2nd Surface screen (Pre-Dive check)

Regards,
Matthias

[wrobell]

heinrichsweikamp Wrote:
-------------------------------------------------------
> Hello,
>
> While I can not confirm all of your errors above,
> the current list have (Without any order):
> - Improve stand-alone simulator
> - Replace mid-size font
> - More features in Gauge and Apnoe mode
> - Use other 50% of external memory for the
> logbook
> - On-Time, Sleep-Time counter for more accurate
> battery sign
> - Improve Onboard-Logbook functions
> - 2nd Dive screen for the blind
> - 2nd Surface screen (Pre-Dive check)

that looks very nice

about the logbook errors. i can
- provide memory dumps (fetched with command 'a')
- try to replicate logbook errors and provide detailed description to you

does it make sense? if you are going to rewrite completely the logbook part,
then probably not... but if you are planing to improve current code, then
maybe my input could be useful for you?

[heinrichsweikamp]

The main issue was a bug in one of the beta which resulted in wrong saved dives. These faulty dives also affect the behavior of the new 1.29. This is not a nice solution but "Delete all" dives will completely format the profile memory...

regards,
Matthias

[wrobell]

thanks for the info. i will start with that then.