Running MacOS 10.15.5, Jamulus version 3.5.6, server and client on the same machine, and client connected to the server.
Minimize the server window.
Quit the client by clicking the red close button on the client window or COMMAND-Q.
Results:
The client window closes.
AND one of these things happens:
-
The server window closes too! (CTRL-click on server icon -> no "show all windows" available, so the server appears to be dead) but apparently the server is still around since top --> Two Jamulus processes still running. If you try to launch JamulusServer by clicking on the icon, you get a "Network Error: Cannot bind socket (maybe the software is already running?)", OR
-
The server window can be restored; it has not been closed. The server is still running. The client (now dead) is still in the connections list.
IF in the case of #1 above, you then kill the Jamulus server process and restart the Jamulus server by clicking on the icon, the Jamulus Server window opens, and
the client is in the connections list (but it hasn't been connected to this instance of the Server).
IF in the case of #2, you restart the client and connect to the server again, everything is apparently fine (no duplicate connection or anything else strange).
Running MacOS 10.15.5, Jamulus version 3.5.6, server and client on the same machine, and client connected to the server.
Minimize the server window.
Quit the client by clicking the red close button on the client window or COMMAND-Q.
Results:
The client window closes.
AND one of these things happens:
The server window closes too! (CTRL-click on server icon -> no "show all windows" available, so the server appears to be dead) but apparently the server is still around since top --> Two Jamulus processes still running. If you try to launch JamulusServer by clicking on the icon, you get a "Network Error: Cannot bind socket (maybe the software is already running?)", OR
The server window can be restored; it has not been closed. The server is still running. The client (now dead) is still in the connections list.
IF in the case of #1 above, you then kill the Jamulus server process and restart the Jamulus server by clicking on the icon, the Jamulus Server window opens, and
the client is in the connections list (but it hasn't been connected to this instance of the Server).
IF in the case of #2, you restart the client and connect to the server again, everything is apparently fine (no duplicate connection or anything else strange).