Reported by geoff on 2010-09-18 22:04
It occurs to me that there are times when it's not possible to get to the NVDA log, due to some kind of crash. This requires the use of another screen reader to retrieve the log, as a restart of NVDA will remove the log in question and replace it with a new one.
I propose that, upon start-up, NVDA rename the current log to a backup name, removing the previous back-up if there is one, and provide some means for accessing this back-up in the log viewer, etc. This would remove the dependence on another screen reader in those situations where it's not possible to use NVDA to retrieve the log.
Reported by geoff on 2010-09-18 22:04
It occurs to me that there are times when it's not possible to get to the NVDA log, due to some kind of crash. This requires the use of another screen reader to retrieve the log, as a restart of NVDA will remove the log in question and replace it with a new one.
I propose that, upon start-up, NVDA rename the current log to a backup name, removing the previous back-up if there is one, and provide some means for accessing this back-up in the log viewer, etc. This would remove the dependence on another screen reader in those situations where it's not possible to use NVDA to retrieve the log.