|
|
This is a dialog used to customize or configure toolbars
This dialog only works if your application uses the XML UI framework for creating menus and toolbars. It depends on the XML files to describe the toolbar layouts and it requires the actions to determine which buttons are active.
Typically, you would include the KStdAction::configureToolbars standard action in your application. In your slot to this action, you would have something like so:
KEditToolbar dlg(actionCollection()); if (dlg.exec()) { createGUI(); }
That code snippet also takes care of redrawing the menu and toolbars if you have made any changes.
Note that the procedure is a bit different for KParts applications. In this case, you need only pass along a pointer to your application's KXMLGUIFactory object. The editor will take care of finding all of the action collections and xml files. The editor aims to be semi-intelligent about where it assigns any modifications. In other words, it will not write out part specific changes to your shell's xml file.
An example would be:
KEditToolbar dlg(factory()); if (dlg.exec()) ...
|
Constructor for apps that do not use components. This is the only entry point to this class. You @bf must pass along your collection of actions (some of which appear in your toolbars). The other two parameters are optional.
The second parameter, xmlfile, is the name (absolute or relative) of your application's UI resource file. If it is left blank, then the resource file: share/apps/appname/appnameui.rc is used. This is the same resource file that is used by the default createGUI function in KTMainWindow so you're usually pretty safe in leaving it blank.
The third parameter, global, controls whether or not the global resource file is used. If this is true, then you may edit all of the actions in your toolbars -- global ones and local one. If it is false, then you may edit only your application's entries. The only time you should set this to false is if your application does not use the global resource file at all (very rare)
Parameters:
collection | The collection of actions to work on |
xmlfile | The application's local resource file |
global | If true, then the global resource file will also be parsed |
|
Constructor for KParts based apps.
The one and only parameter, factory, is a pointer to the XML GUI factory object for your application. It contains a list of all of the GUI clients (along with the action collections and xml files) and the toolbar editor uses that.
Use this like so:
KEditToolbar edit(factory()); if ( edit.exec() ) ...
Parameters:
factory | Your application's factory object |
void |
[protected virtual slot]
Overridden in order to save any changes made to the toolbars
Reimplemented from KDialogBase