In Summary:
Upon an update check being performed, I think logging certain information about the steps carried out by NVDA could greatly assist whilst diagnosing any potential issues that may occur. Whilst understandably it may not make all that much sense to provide output within any error dialogs which may appear, this could be logged so that the user can easily paste this information into an email/issue, etc.
In Depth:
This issue became apparent several days ago when I was in the process of updating NVDA on two machines, both running Next 13096,1c5884d. Whilst one machine updated without issue, I'm currently having a problem whereby the other simply refuses to download the update package after the "Not Now" button has been clicked within the Donation window; I'm simply presented with an error dialog stating that an error downloading the update occurred. Setting the log level to Debug unfortunately doesn't provide me with any useful information - strangely, however, this even occurs after manually downloading an update package, applying the new version, and once again checking for updates. Both machines have been configured exactly the same, and I've been able to carry out an update from within NVDA on this machine before without issues and whilst it's still possible to update my installed copy manually, I'd like to get to the cause of this issue if at all possible.
In Summary:
Upon an update check being performed, I think logging certain information about the steps carried out by NVDA could greatly assist whilst diagnosing any potential issues that may occur. Whilst understandably it may not make all that much sense to provide output within any error dialogs which may appear, this could be logged so that the user can easily paste this information into an email/issue, etc.
In Depth:
This issue became apparent several days ago when I was in the process of updating NVDA on two machines, both running Next 13096,1c5884d. Whilst one machine updated without issue, I'm currently having a problem whereby the other simply refuses to download the update package after the "Not Now" button has been clicked within the Donation window; I'm simply presented with an error dialog stating that an error downloading the update occurred. Setting the log level to Debug unfortunately doesn't provide me with any useful information - strangely, however, this even occurs after manually downloading an update package, applying the new version, and once again checking for updates. Both machines have been configured exactly the same, and I've been able to carry out an update from within NVDA on this machine before without issues and whilst it's still possible to update my installed copy manually, I'd like to get to the cause of this issue if at all possible.