Hello low.flying.pigs;
there was a bug: when restartig GCC, load a track and continue, then immediately the shortest distance between start of track and current position was added to the distance. It should now be fixed but I haven't tested it in real - I think you will do it.
In Versions prior 4.9 tracks was limited to 18 hours but since 4.9 the limit is 68 years, which should be enough.
The odometer should never reset. GccState (with current odo) is written on all major actions (switch on, off GPS; start, stop, pause, continue of tracks; load files and exit GCC. One possibility is a problem with reading the file. Do you have a "LoadState" error in GpsCycleComputer.log? If GCC crashes you should only loose the km since last save of GccState, unless it crashes right in the moment of saving and the file is corrupt.
Attached is version 4.10 beta 2
Klaus
Hello Blaustein / Klaus,
Thank you for the information regarding track limits.
I can confirm GCC 4.10beta 2 resolves the resumed session distance error issue, by whatever method the session is resumed. Excellent work.
What are your thoughts regarding an option to include / exclude the elapsed time since the end of the session being resumed within the 'stop time'? If resuming after a few moments due to an abnormal termination for example, it may be desireable. If resuming after an overnight stop for example, it may well not be.
Regarding the resetting odometer, there were a number of errors in my GpsCycleComputer.log file, including load state errors. I renamed the existing file so GCC would start afresh with a new log file and will carry out some further testing. As far as I can tell so far, something causes the gccstate.txt file to be unreadable / corrupted and it is then overwritten by GCC starting again from zero, there being no other storage of the previous odometer value to restore from. I will let you know any findings. If it just happening when an abnormal termination occurs, that is not to much of issue as that should be rare. If not, it may be more significant. Time will tell.
Something that is perhaps more of an issue are the 'pause', 'stop', 'gps off', and 'X close program' buttons. All work as intended and that is the problem, although no fault of GCC, more the practicalities of cycling and the equipment. I wasn't going to bother mentioning this but since it keeeps happening occasionally, this evening being the latest incident, I thought it better to bring it to your attention.
Occasionally, logging gets interupted unintentionally and goes unnoticed resulting in lost logging. It seems to me a 'press and hold' instead of just 'press' for these functions would largely eliminate the issue (perhaps with the exception 'X close program, it not being part of GCC), at least in most situations I suffer. It is probly more elegant than a popup 'do you really want to' type message.
Incidentally, the 'X close program' button for me if pressed whilst logging, shows a breif message 'GPS is logging do you want to exit stop logging' with a yes or no option. It then promply closes itself without waiting for an answer ending logging regardless.
Again there is no particular hurry to any of this from my point of view, have a good weekend.
Let me know if you need any further information or testing.
low.flying.pigs