The disconnection is only detected when trying to send a LX200 command. This is quite fast with the mount driver, which constantly polls the server, but depends on current activity for the guider and focuser. Anyway, opening the guider or the focuser alone must be a very uncommon use case.
Upon disconnection, the drivers are cleanly stopped as if it were a disconnection on user's request ; but, as it was not, the connection property is put in alert state.
This change was tested on macOS x86_64 and Linux ARM.
The disconnection is only detected when trying to send a LX200 command. This is quite fast with the mount driver, which constantly polls the server, but depends on current activity for the guider and focuser. Anyway, opening the guider or the focuser alone must be a very uncommon use case.
Upon disconnection, the drivers are cleanly stopped as if it were a disconnection on user's request ; but, as it was not, the connection property is put in alert state.
This change was tested on macOS x86_64 and Linux ARM.
Fixes #457