Hi there, I just fixed a crash when the Windows system is about to closed and then be canceled. Putty-nd's resource then enter a releasing state and can't be run forward. The new fixed binary is as the attachment. But I am not sure if it is the same issue. If the crash happens, there should be a file like PuTTY-nd-vv8.4p3.crashreport under the same directory with the putty-nd.exe. It is the plain text callstack of the crash. It can help to identify the crash issue.
Hi there, please check the attachement. The font size is adjusted and the context menu is removed. I am glad you like this feature. It has not been changed for years, I don't know how these issues come up...
Hi there, please check the attachement. The font size is adjusted and the context menu is removed. I am glad you like this feature. It has not been changed for years, I don't know how these issues come up...
Hi there, I left the app open for the weekend, but the no response "+" button does not happen yet. I want to ask how often does it happen?
Hi there, thanks for the logs. The logs shows that it doesn't hide the cursor itself at all during the test. It could be the system's behavior, which I can't identify. And I make another build to show the cursor explicitly for each session when it starts. And hope this workaround would help.
I had a try last weekend but failed to reproduce the issue. I have to write some logs to see what happens. Please help to run the attachement. Then send the file named debug.log at the same directory with the exe file to me. thx!
cool! I can sync it back when it is done.
Yes, I should put this in the readme.