From 10308be19ef7fa44699562cc75946e7ea1fdf6b9 Mon Sep 17 00:00:00 2001 From: tpearson Date: Fri, 7 Jan 2011 03:45:53 +0000 Subject: Revert automated changes Sorry guys, they are just not ready for prime time Work will continue as always git-svn-id: svn://anonsvn.kde.org/home/kde/branches/trinity/kdelibs@1212479 283d02a7-25f6-0310-bc7c-ecb5cbfe19da --- kdeui/kedittoolbar.h | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'kdeui/kedittoolbar.h') diff --git a/kdeui/kedittoolbar.h b/kdeui/kedittoolbar.h index 4bc6c26b4..9033ff17f 100644 --- a/kdeui/kedittoolbar.h +++ b/kdeui/kedittoolbar.h @@ -43,7 +43,7 @@ namespace * * 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 tqlayouts and it requires the actions + * files to describe the toolbar layouts and it requires the actions * to determine which buttons are active. * * Typically, you would include the KStdAction::configureToolbars() @@ -83,7 +83,7 @@ namespace * 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 - * tqfinding all of the action collections and XML files. The editor + * 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. @@ -164,7 +164,7 @@ public: * Constructor for KParts based apps. * * The main parameter, factory(), is a pointer to the - * XML GUI factory object for your application. It tqcontains a list + * 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. * @@ -261,7 +261,7 @@ private: * * This widget 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 tqlayouts and it requires the actions + * files to describe the toolbar layouts and it requires the actions * to determine which buttons are active. * * @author Kurt Granroth @@ -325,7 +325,7 @@ public: * Constructor for KParts based apps. * * The first parameter, factory, is a pointer to the XML GUI - * factory object for your application. It tqcontains a list of all + * 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. * -- cgit v1.2.1