At the moment, if one uses "xpra upgrade" on an existing xpra session, winswitch will see that the server process it had started has now terminated and it will close the session and kill all the remaining session processes.

Options:

• detect an exit code from the xpra server which will mean "upgrade me" and re-spawn it.

This could be tricky as there are daemons involved, pipes and file descriptors, gio file watchers, etc.

• change the xpra code to exec the new process in place so we keep the same pid and this becomes transparent to winswitch

Another benefit is that all the start options would then be preserved too (password, etc) - and we could even envisage that extra options could be specified to override existing ones

With r4481 of winswitch I've got a corrupted settings window - the window is too small for the "users" tab of the server settings, see screenshot.

I'm using a manual "ssh -L 8022:host1:22" to get winswitch to tunnel to another host2. Now, when that times out, winswitch doesn't seem to correctly "get" it - in the menu is the application listed as "Re-connect", although the server menu shows "Connect" (so the application entry shouldn't even be there - right?)

I think that the menu shouldn't show the application if the server is not connected.

Furthermore, «are you saying that you should not be able to connect to an app if you have lost connection to the winsiwtch server it is on? if so, yes, that should not be possible» too ;)