[Touch Diamond, MDA Compact IV General] low.flying.pigs:
It would seem apparent that if GCC last operated in that manner as at 4.4 released October 2010, that users in fact prefer the current implementation they have been familiar with and using for over three years without complaint and that therefore ought to be retained fundamentally unaltered. That remains the case, it has been expressed, and the actual issue did not relate to GPS being switched off in the first instance.

The current functionality when GPS is switched off is neither an error or a bug. If was not what was intended, it is nonetheless what should have been intended, and is indeed what users prefer and are accustomed to as aforementioned.

However, the start button shown after pause when GPS is switched off, should actually be the continue button, as that is the function hence the Continue log file prompt, as logging is stopped and no longer paused, as there is nothing to log without GPS signal, but the session is open, and either continued by selecting yes, or that saved and a new session and file started by selecting no. In both instances GPS then switches back on automatically.

Changing the button involves nothing more than changing the button icons, and would correctly distinguish the functions, start starts the session initially, continue continues or not an open session. (the continue button on the Menu page essentially automatically selects yes)

Pause is dictionary defined as to interrupt an action briefly, a temporary stop in action. There should be no such thing as long pause, being the opposite of brief. The so called long pause is actually the temporary stop. The importance is not the words, the importance is the functionality when GPS is on, and GPS is off. To elaborate:

When GPS is not switched off, GCC behaves as it should, the pause button remains a pause button, unpause and GCC continues logging without prompt.

When GPS is switched off, GCC behaves as it should, logging having been stopped as there is nothing to log with GPS off, when resuming GCC prompts the user whether to continue the log or start another, by design, introduced for good reason in 4.6, as whilst the user wishes to continue logging, whether to continue the existing log or start a new one is their choice. The proposed solution detailed in post 2161 inherently caters for when a user does not wish to see the prompt in this circumstance, and would always to want to continue an existing log.

The current functionality when GPS is not switched off but a loss of signal occurs, which was the actual issue in the first instance, is resolved by the proposed solution detailed in post 2161 and does not affect existing functionality.

In addition to the proposal, the behaviour of prompts in general could be adapted so that in event of a prompt: If the screen is off, it is switched on, to enable the user to see the prompt. GCC currently produces and audible alert when a prompt occurs. Whether or not that sound is heard from GCC depends currently on Windows Sound and Notification settings (name varies dependent on OS version). GCC could include an option to switch on / override those settings as required whilst running allowing it's sounds to be heard. GCC already overrides other Windows settings. If the users attention is not forthcoming, the sound could recur periodically until the prompt was attended to.

A useful prompt could occur in another circumstance: If GPS is on, and there is movement but GCC is not logging, a prompt could alert the user, as they may have set off having forgotten to start logging.

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

Further information to be added.

low.flying.pigs