Hello,
In our application we use a usercontrol (usrCtrl) which contains a UltraToolbarsManager (utmMain).There are multiple instances of this usercontrol in different forms.Every usercontrol has a unique name (Example: usrCtrl_1, usrCtrl_2, ...... ,usrCtrl_n).Before closing one of the forms we implemented these two steps:1. setting the usrCtrl_n.utmMain.SettingsKey to the unique name of the usrCtrl_n.(Example: usrCtrl_1.utmMain.SettingsKey = usrCtrl_1.Name)2. Then we call usrCtrl_n.utmMain.SaveComponentSettings().When we reopen the form we use the Form.Load event to do following steps:1. set again the usrCtrl_n.utmMain.SettingsKey to the unique name of the usrCtrl_n.2. Then we call usrCtrl_n.utmMain.LoadComponentSettings().So for every usercontrol instance the user configurations for the usercontrol's UltraToolbarsManager are saved and reloaded properly.
Until now it worked great....But a few days ago we published a new version of our application which contains new tools in the usercontrol's UltraToolbarsManager. Now our problem is that the user can't see the new tools. It seems like that the loading of the saved component settings completely overwrites the designed UltraToolbarsManager settings.What can we do to prevent this behaviour so that the new tools appear and the user configuration takes effect too?
Best regardsisiraider
Hello Dave,
unfortunately there is no solution for our problem with the UltraToolbarsManager. So we have to wait until the feature is ready. I know that this can take a while... My boss is a little bit angry because we announced some new functionalities to our user and now nobody can see/reach them. So we have to publish these functionalities otherwise. You can close this thread.
Thank you and best regards
Hello Isiraider,
Has this issue been resolved or do you have any other questions I can help you with?
Sincerely,
You can either keep an eye out for our "What's New" release announcements, or send an email to one of our Product Managers at andrewf@infragistics.com or murtazaa@infragistics.com for more information.
thank you very much! I hope that I will get an information when the feature request is developed? :)
I will be logging a feature request on your behalf for the functionality you want. In the meantime, however, you could use the SaveAsXml method to save the settings to a SOAP format XML file. Then, when the application loads, use an XmlReader to iterate through the saved settings and compare them with the current settings. Each tool has a unique Key property that you can use when comparing.