Commands not processed if connection is lost

Let's say you are connected to a site, or so FlashFXP believes, and enter in a raw command in the raw command line. FlashFXP figures out that it is no longer connected and displays the connection has been lost. However, it does not automatically reconnect to the site to process the command. Instead, you must input the command again and then it starts to connect, and once connected, it will process the command.

[L] MKD Test
[L] Connection lost: SomeFTP (Duration: 1 hour 34 minutes 24 seconds)
[L] Connecting to SomeFTP -> IP=111.111.111.111 PORT=21
[L] MKD Test

Not sure if this happens if you just double click on a directory or something too, but it for sure happens with the raw command line input. By design or a bug? Ty.

v4.2.2 b1760

Prior to issuing the command FlashFXP attempts to detect if the connection is still active and ready, unfortunately it appears that in your situation this detection failed to detect the dropped connection.

I suspect that the connection loss is detected during the actual execution of the command and because the connection loss occurs during the command no attempt is made to re-connect and retry it.

The reason no re-connect attempt is made is because during the context of the execution the current state is unknown, it doesn't know if this command is part of a series of commands or just a single command unrelated to any previous commands and re-reconnecting here could execute the command in the wrong context or wrong location.

To help customers with unreliable network connections we disable the TCP/Socket keep alives while idling, however if keep alives were active this connection lost would of been detected immediately rather than in a situation where it was too late to do anything useful.

I will see what can be done to improve this situation.

I forgot to ask what version of Windows are you using?

Windows 7 x64.

Looks like this one has been fixed in the current v4 build. Thanks