Professional UI Solutions
Site Map   /  Register


Please Log In to post a new message or reply to an existing one. If you are not registered, please register.

NOTE: Some forums may be read-only if you are not currently subscribed to our technical support services.

Forums » Prof-UIS General Discussion » Toolbar serialization Collapse All
Subject Author Date
Peter Nalyvayko Jun 17, 2008 - 11:19 AM

After the toolbar state has been deserialized, how do I find out which toolbars have been affected? For example, I need to perform a special action such as displaying a hidden toolbar if the toolbar state was not previously serialized. The framework I am working on consists of static and dynamic toolbars (not known at compile-time) so after loading the toolbar state I’d like to display the toolbars which states were not serialized.

Technical Support Jun 19, 2008 - 5:58 AM

The states of all the toolbars are always saved and loaded. If you are using simple non-customizable toolbars, the number of toolbars is always static. In the case of customizable toolbars and menus there are two types of toolbars:

1) Basic toolbars. Count of basic toolbars is always static.

2) Toolbars allocated by the user.

The toolbar state saving in the customizable application is done in two steps:

1) Saving the state of CExtCustomizeSite, when information about the toolbars allocated by the user is saved . The identifier of each toolbar and all its buttons are also saved.

2) Saving the state of all toolbars currently created in the frame window.

The toolbar state loading in the customizable application is done in two steps:

1) Loading the state of CExtCustomizeSite. All toolbars allocated by the user become created at this step.

2) Loading states of all toolbars.

Although the total number of toolbars is variable in customizable applications, the control bar state saving and loading code always deals with the same count of toolbars because the CExtCustomizeSite class re-creates all the dynamic toolbars during its state loading.