Thank you, I have never captured enough data to find out what really happens. That is what I suspected that Garmin would do. I still do wish that we were given a lot more space for this data, but it is more a developer thing and not something that most users even know is possible.
You have a 5k log file, and when that fills, it's copied as a backup, and the new file starts clean. If it fills again, it over-writes the backup and starts clean again. So the most you can have in the two files is 5k to about 10k.
Using Sys.printXX is an expensive op (time, etc) on a real watch and is really just a debug tool to be used sparingly...
Have you considered using the FitContibuter stuff? Start recording and with the data is in the .fit, users can see it as a graph on GC and not have to deal with a the .txt log file?
You have a 5k log file, and when that fills, it's copied as a backup, and the new file starts clean. If it fills again, it over-writes the backup and starts clean again. So the most you can have in the two files is 5k to about 10k.
Using Sys.printXX is an expensive op (time, etc) on a real watch and is really just a debug tool to be used sparingly...
Have you considered using the FitContibuter stuff? Start recording and with the data is in the .fit, users can see it as a graph on GC and not have to deal with a the .txt log file?
I log data when the application starts and once a minute thereafter. In this case .. a FIT file would maybe not be a great option ? I also expect that few will actually use this feature ... but I do. Maybe something for a new version but right now .. not going to happen as my app should go for approval as early as today.
