|
|
|
|
|
What’s new in version 1.1.01?1) Dynamic toolbar layout It
is now possible to add more buttons to the toolbar after the toolbar has
been initialized from the XML file. This can, for example, be used to
implement dynamic “Highlight and Word Find” buttons, similar to the ones
the Google Toolbar has. The Google Toolbar adds a new button to the
toolbar for each word or phrase contained in a query when a search is
performed. Each button finds the next occurrence of a word or a phrase on
the current web page. 2) Toolbar reconfiguration The
toolbar can now be reinitialized from a new XML configuration file at any
time. This can, for example, be used to completely change the toolbar
layout after a user logs in to a web site, assuming that the user has
access to more functionality after he logs in. 3) Access to text entered in edit and combo-box controls The text entered in an edit or combo-box control could previously only be obtained when the user pressed the enter key, or selected an item in a combo-box drop-down list. The command object associated with an edit or combo-box control is now continuously updated when the user enters text. This is useful, for example, when implementing a toolbar with multiple search buttons all relating to a single search box. The current text can be read from the search box when one of the buttons is clicked.
InterfacesToolBandI (changed) The new member function GetControlCollection() returns a control collection interface, which can be used to dynamically change the toolbar layout. The
method DeleteAllControls() has been deleted. Similar functionality can be
achieved by using the control collection interface. CommandI (changed) The
new member function DoUpdateText() is called by the framework to update a
command object as text is entered in a edit or combo-box control. The
method is intended for internal use only. ControlI (changed) A new member function, GetControlCollection(), has been added to the interface. The method returns a control collection interface, if the control is a menu control, and NULL otherwise. The control collection interface can be used to dynamically change the content of menus in the toolbar. The
member function AddControl() has been deleted. Similar functionality can
be achieved by using the control collection interface. ControlCollectionI (new) The control collection interface makes it possible to dynamically add or remove buttons from a toolbar, or a menu in a toolbar. The interface contains member functions for adding controls and for removing controls. The interface can also be used to examine the current controls in a toolbar.
ClassesToolBandContextC (changed) The
new member function, DeleteCommand(), deletes a command object previously
added with The new member function, GetToolBand(), returns a toolband interface which can be used to dynamically change the toolbar layout. The
new member function Reconfigure() makes the toolbar reinitialize from a
new XML file. CommandC (changed) The
new member function DoUpdateText() is called by the framework to update a
command object as text is entered in a edit or combo-box control. The
member function is intended for internal use only. 3) CommandPointerSetC (new) The
class is a helper class. It stores a set of references to commands. A
command pointer set can be used to keep track of commands created
dynamically, for example “Highlight and Word Find” commands. 4) ControlPointerSetC (new) The class is a helper class. It stores a set of references to controls. It can be used to keep track of controls created dynamically, for example “Highlight and Word Find” buttons. Information about the current controls in a toolbar are returned as control pointer sets.
|
||
|
© 2002-2008 Diodia Software |