After a refused connection the retry timeout is reset to 30s when mouse enters the window
I work with a website that, for security reasons, disables SSH/SCP/SFTP connections after a period of no usage.
If I attempt to connect WinSCP when connections are disabled, the connection fails, and WinSCP then waits 30 seconds to retry.
I move my mouse over to a different window, and enable the SSH listener. I then move back to the WinSCP window, which is counting down towards 0 and then retry the connection. Let's say, for example, that there is 7 seconds left on the countdown.
On the mouse entering the window, the counter resets to 30 seconds, which is annoying!
I can't think of a reason why this should happen, rather than allow the countdown to continue from its current value?
Regards
[WinSCP 6.6.2 RC, but it's happened in many previous versions, Windows 11]
If I attempt to connect WinSCP when connections are disabled, the connection fails, and WinSCP then waits 30 seconds to retry.
I move my mouse over to a different window, and enable the SSH listener. I then move back to the WinSCP window, which is counting down towards 0 and then retry the connection. Let's say, for example, that there is 7 seconds left on the countdown.
On the mouse entering the window, the counter resets to 30 seconds, which is annoying!
I can't think of a reason why this should happen, rather than allow the countdown to continue from its current value?
Regards
[WinSCP 6.6.2 RC, but it's happened in many previous versions, Windows 11]