When the core client has set a password for GUI RPCs and the Manager is not started in the client's data directory, the Manager complains that it cannot read the password from the gui_rpc_auth.xml file because it cannot find this file. To still connect to the local client, one needs to select localhost and type in the password at the "Select Computer" dialog. To control the client with a remote Manager, one always has to type in hostname and password at the "Select Computer" dialog.
It would have two advantages if the Manager would save the hostname/password pair entered at the "Select Computer" dialog in its config file. First the Manager would be able to connect to the local client although it wasn't started in the client's data directory and secondly the hostname/password input widgets could complete hostnames and preselect passwords. The only drawback of this proposal is that the passwords probably need to be saved in cleartext in the configuration file.
