coralslave instantly closes if output folder not specified
Opened this issue · 1 comments
mrindar commented
If the output folder specified when starting coralslaveprovider does not exist, the coralslave window will instantly close while coralslaveprovider and coralmaster remains silent. This can lead to a lot of confusion since it is not obvious that the problem is the fact that the output folder does not exist. coralslave does appear to write some error message to the terminal window, but it closes so quickly that it is impossible to catch.
mrindar commented
It might be an idea to have a switch in coralslaveprovider to say that coralslave should write everything that goes to standard output, to a file.