[Touch Diamond, MDA Compact IV General] low.flying.pigs:
When logging, if pause is pressed, the stop button becomes the GPS button allowing GPS to be turned off. If GPS is turned off logging is stopped as would be expected, there being nothing to log with GPS off. The pause button then becomes the start button as would be expected as logging has been stopped, the only action available being to start. If start is pressed, whether or not GPS has been turned back on, a prompt appears asking Continue log file Do you want to continue the track log into file: Yes No Cancel. This is as would be expected as the the user may or may not wish to continue logging to the same log, or at all, and press Yes No or Cancel accordingly. If selecting Yes or No, GPS, if it was not already on turns on and logging resumes to the same log or a new log is started.

This did not go unnoticed. This was considered normal intended behaviour, to be expected, and as such there was nothing to report. Consequently there would appear nothing to fix.

Incidentally, Continue log file prompt functionality was introduced approximately three years ago in April 2011, following any 4.6 betas, in 4.6 Final. According to ReleaseNotes.txt "new features: - if the track log is stopped (or loaded from disk), and the start log button is pressed again, the user is now asked, if he want´s to continue logging into the existing log file."

However, the existing Continue log file prompt behaviour could be adapted:

It could be made not to trigger in any circumstance unless GPS has been switched off.

It could be made optional with a Confirm 'Continue log file' feature on Options Main screen similar to the existing Confirm 'Pause' and 'Stop' which would resolve any unwanted appearance of a Continue log file prompt. The new option could be integrated with that or separate which would give the most versatility to any user that requires one prompt or the other, but not both. When Confirm 'Continue log file' (on by default for safety) is switched off, an existing log present would be continued. The existing intelligence could still be applied to this and enhanced so that even when Confirm is off, in the same way a warning is displayed if over a kilometre distant from last position, that warning could still display, as could an additional warning when there is a time discrepancy in excess of a limit since time of last position. In those circumstances a user may not actually want to automatically resume. There may be other such circumstances. This would allow Confirmation off to not interfere where undesired, but still intervene other markedly different situations as a safety measure.

* Incidentally, in my testing, merely by pausing logging, then loosing signal, then unpausing before signal acquisition, a Continue log file prompt could not be observed to appear upon pressing pause again to resume logging, or when signal was reacquired. This was considered normal and to be expected, as the logging has not been stopped, only paused, and as the logging session is the same, it is inherently obvious it is wished to resume.

Screen alone being off had no effect on this, nor did screen off with 'Safe Energy: GPS off on power off' selected. GPS was however off with the screen, the GPS indicator no longer being green when the was screen turned back on, but red, followed by yellow for 1 second for each drop point, then green.

Only when the GPS was deliberately switched off after pausing, by pressing the GPS button, and then pressing start was the prompt observed, considered normal as previously detailed. It is noted it was not however described that the GPS was being switched off or that start was then pressed.

Nonetheless, whatever the circumstance, the aforementioned proposed solution which resolves currently foreseeable unwanted prompt issues will suffice.

It can be stated any changes would not adversely affect any existing functionality or user.

Further information to be added.

low.flying.pigs