You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When selecting the connect button in the header twice for the same robot without disconnecting, this will result in a non-ready state due to the port's streams already being locked
It would be nice to check for the following 2 scenarios
The cause of the failed connect is that the same robot is already connected
We should probably immediately throw a ready state or trigger a reconnect by reserving the old port
The cause of the failed connect is that another program is already using it
Instead of simply throwing a non-ready state and keeping the user guessing as to what went wrong we may want to show a popup to indicate the reason for the failed action
The text was updated successfully, but these errors were encountered:
When selecting the connect button in the header twice for the same robot without disconnecting, this will result in a non-ready state due to the port's streams already being locked
It would be nice to check for the following 2 scenarios
The text was updated successfully, but these errors were encountered: