| Description | Consider an organization that provides one or more parallel visualization cluster resources and also distributes ParaView on the systems for users to take advantage of them. In the system setup of ParaView, there will be a site-specific default_servers.pvsc file defining how the connections are made.
When a user first starts ParaView, these connection definitions are copied into the user's local servers.pvsc file. The intention is to save the server launching arguments the user last used as the default for the next invocation (see closed bug 0005487).
The problem is that the system administrators will inevitably have to make changes to how server connections are made, which will be done to the system-wide default_servers.pvsc. However, because ParaView has already copied the old definitions to the user's personal server connection settings, the old entries override the new entries.
The solution to to change the behavior of ParaView to NOT copy the system server connection settings to the user's personal server connections file. Instead, the values to use for the server connections should be stored in the user's .ini file, separate from the server connection definitions. So when ParaView goes to connect to a server, it first reads the connection definitions from the appropriate pvsc files. It then gets the default arguments from the user's .ini settings file and, if they exist, overwrite the defaults in the pvsc file. On a successful connection, new default settings are saved back to the .ini settings file. No changes to any .pvsc file happens unless the user has "added" or "edited" one of the connections (and the user should probably not be able to edit one of the system connections, which I think was the behavior a while ago). |