summaryrefslogtreecommitdiffstats
path: root/tdeui/TODO.xmlgui
diff options
context:
space:
mode:
Diffstat (limited to 'tdeui/TODO.xmlgui')
-rw-r--r--tdeui/TODO.xmlgui8
1 files changed, 4 insertions, 4 deletions
diff --git a/tdeui/TODO.xmlgui b/tdeui/TODO.xmlgui
index 3c3d4f8a4..0c0753685 100644
--- a/tdeui/TODO.xmlgui
+++ b/tdeui/TODO.xmlgui
@@ -4,15 +4,15 @@ When removing an xmlgui-client involves destroying toolbars, we need to save the
whole set of toolbar positions of the mainwindow, into the xmlgui-client.
Data structure:
-struct KToolBarPos {
+struct TDEToolBarPos {
short int index;
short int offset;
bool newLine;
};
-typedef QValueVector<KToolBarPos> KToolBarPosList;
+typedef QValueVector<TDEToolBarPos> TDEToolBarPosList;
API:
-KToolBarPosList KMainWindow::toolBarPositionList() const;
+TDEToolBarPosList TDEMainWindow::toolBarPositionList() const;
The remaining problem is to know when to call it:
* when we know in advance that we'll be able to remove toolbars?
@@ -74,7 +74,7 @@ which would forward the action() and domElement() calls - because a client
can be in only one factory at a time.
This custom builder needs to know about action plugging too, we don't really want
-to call KAction::plug here. So this would be 'virtualized' (new virtual, in a new
+to call TDEAction::plug here. So this would be 'virtualized' (new virtual, in a new
interface to keep BC, that by default calls plug, but does something else in
kedittoolbar's builder).