Small UX update to handle when Rojo unexpectedly quits due to an error.
Currently, if Rojo crashes, there is no indication of such - this can be confusing (especially for newer developers), as the button still indicates that a server is running, and you do not realise that the server has stopped until you explicitly open up the output of the extension and check.
This PR implements a new state to the button: "Crashed". If Rojo exits with a non-zero exit code, then we set the button state to "crashed". We also automatically open up the Rojo console output, so that the end user can quickly see the error that occured.
Small UX update to handle when Rojo unexpectedly quits due to an error. Currently, if Rojo crashes, there is no indication of such - this can be confusing (especially for newer developers), as the button still indicates that a server is running, and you do not realise that the server has stopped until you explicitly open up the output of the extension and check.
This PR implements a new state to the button: "Crashed". If Rojo exits with a non-zero exit code, then we set the button state to "crashed". We also automatically open up the Rojo console output, so that the end user can quickly see the error that occured.
Closes #31