Hello,
I have encountered a problem where removing and adding a plugin with different options results in SDL Trados Studio 2011 using the options from previously added plugin. (Restarting the application resolves this)
I emailed sdk-feedback about this problem, and they suggested that storing settings the way we did was "non-canonical".
Hence, the question is what is the correct way to store settings?
What we have is this:
ITranslationProvider class which has a SOAP client object with the users username and password (which it needs to authenticate for the users machine translation systems) which is then used by ITranslationProviderLanguageDirection:: SearchSegment. It seems that ITranslationProviderLanguageDirection uses the ITranslationProvider object from the plugin that was removed. I have trouble seeing how any other way to store the soap object containing the username and password.
It is worth mentioning the user can see and select the systems in the “project options”, but as the user tries to translate the old object is used he uses the previously selected system and credentials.