Please change client to remember the path to the client.conf that was used to start the gui. This will fix some problems that are caused by starting with one client.conf, but then then tool using only the default located client.conf when running the gui.

It is possible to start the gui and specify an alternative client.conf. This feature has been there as long as I can remember. It is a great feature for admin and also nice for teams that share a PC login (our use case is PCs used on Lab/Bench test setups). You do this by starting gui with "-clientconf" parameter.

The problem is, this alternative client.conf file is not remembered. This causes problems in at least 2 areas, and inconvenient in others.

Problems:
1) If you use the in gui option to switch to the other gui (legacy to new, or new to legacy) it uses the default client.conf which can mean logged in as a different user, as well as other different options.
2) Makes using Dynamic Workspaces basically incompatible with using alternative client.conf files for startup (at least when using a different user to login with between different client.conf files).

In addition, this can be worked around but is annoying... All settings such as last WS, colors, Preference settings, etc that I do within the gui session are saved only to the default client.conf. If I want different setting for an alterative client.conf, I have to edit the client.conf manually. This can also cause a problem for some settings like last WS if the user specified in both client.conf files do not have the same permission.