When a user changes their mind about recording a solve to the file after they have started inspection / started the solve time. The reasons can be varied, some of them are:
they got distracted / someone was at the door / their phone started ringing
they are unwilling to commit the time to the file (it's too high relative to their average time. Happens to me some times, if I am not paying enough attention)
the occurrence of a significant unconceivable event
The idea is to have a particular key which if pressed when the user is either inspecting or solving, then the current solve is trashed (not written to file, not added to current session either) and the screen goes back to showing a scramble for a new solve.
The feature it provides should be kept however or at least replaced with something similar. Canceling the current solve maybe? It should just reset everything and write a 'DNF' (or maybe nothing at all) if you get disturbed during the solve.
When a user changes their mind about recording a solve to the file after they have started inspection / started the solve time. The reasons can be varied, some of them are:
The idea is to have a particular key which if pressed when the user is either inspecting or solving, then the current solve is trashed (not written to file, not added to current session either) and the screen goes back to showing a scramble for a new solve.
courtesy @Jan-Ka
original comment