Exception handling: Disconnected from ETP Server 10054

[klim]

Hi David

Please see below my suggestion.

Case:
"Everything" is configured to use ETP-Server to use remote Index and "Everything" is running, doesn't matter if active or inactive.
In case of a network interruption, the socket connection to the ETP-Server breaks off immediately and "Everything" throws an error (See attached file), even if "Everything" was not in used at that time.
Meanwhile, the network connection has been restored, but "Everything" message still appears in screen. In VPN Environments, this behavior will often happen in case of unreliable connection. The user has to accept that message before using "Everything" again, even if the user doesn't recognized that network outage, but now he knows that for sure.

Suggestion:
Instead of throwing an error instantly and pushing that to the screen, do exception handling in background and:
1) reconnect ETP connection automatically in case of restored network connection
2) if network connection is still not restored, popup the message later. Maybe when window is active again or at least when user types into "Everything" search bar.

[void]

Reconnecting to an ETP server on disconnection is on my TODO list.

Thank you for the suggestion.



For now, please consider the Everything Server.