From d2728dd8dbad48f045a5eca1899924df15633a89 Mon Sep 17 00:00:00 2001 From: Michele Calgaro Date: Mon, 25 Sep 2023 13:57:48 +0900 Subject: Replace QObject, QWidget, QImage, QPair, QRgb, QColor, QChar, QString, QIODevice with TQ* version Signed-off-by: Michele Calgaro --- doc/api/HowToAddPlugins.dox | 6 +++--- doc/api/HowToAddProgrammingLanguages.dox | 8 ++++---- doc/api/PropEditor.dox | 4 ++-- 3 files changed, 9 insertions(+), 9 deletions(-) (limited to 'doc/api') diff --git a/doc/api/HowToAddPlugins.dox b/doc/api/HowToAddPlugins.dox index 3f9d1b20..e40840a8 100644 --- a/doc/api/HowToAddPlugins.dox +++ b/doc/api/HowToAddPlugins.dox @@ -85,7 +85,7 @@ Your part must be derived from KDevPlugin. - KDevPlugin takes two arguments: - 1) A parent argument. This also comes from createPartObject(). - - 2) A name, which in turn is given to the QObject + - 2) A name, which in turn is given to the TQObject constructor. . . @@ -134,7 +134,7 @@ rooted in the dom document node. For example, the autoproject part uses the statement 
-    QString cflags = DomUtil::readEntry( *part->document(),
+    TQString cflags = DomUtil::readEntry( *part->document(),
                                          "/kdevautoproject/cflags" );
@@ -181,7 +181,7 @@ void GDBBreakpointWidget::savePartialProjectSession(QDomElement* el) { BreakpointTableRow* btr = (BreakpointTableRow *) m_table->item(row, Control); Breakpoint* bp = btr->breakpoint(); - QDomElement breakpointEl = domDoc.createElement("breakpoint"+QString::number(row)); + QDomElement breakpointEl = domDoc.createElement("breakpoint"+TQString::number(row)); breakpointEl.setAttribute("type", bp->type()); breakpointEl.setAttribute("location", bp->location(false)); breakpointEl.setAttribute("enabled", bp->isEnabled()); diff --git a/doc/api/HowToAddProgrammingLanguages.dox b/doc/api/HowToAddProgrammingLanguages.dox index 9ef228e2..78091009 100644 --- a/doc/api/HowToAddProgrammingLanguages.dox +++ b/doc/api/HowToAddProgrammingLanguages.dox @@ -71,10 +71,10 @@ Language support can offer additional features: \subsection sectionAttributeMethodWizard Attribute/Method wizard - add method dialog: (See cpp or java) - - virtual void addMethod(const QString &className); + - virtual void addMethod(const TQString &className); . - add attribute dialog: (See cpp or java) - - virtual void addAttribute(const QString &className); + - virtual void addAttribute(const TQString &className); . . @@ -82,8 +82,8 @@ Language support can offer additional features: If there is a Qt bindings for your language and there is a possibility to use QtDesigner ui files, you could implement ui subclassing feature: - - virtual QStringList subclassWidget(const QString& formName); - - virtual QStringList updateWidget(const QString& formName, const QString& + - virtual QStringList subclassWidget(const TQString& formName); + - virtual QStringList updateWidget(const TQString& formName, const TQString& fileName); . diff --git a/doc/api/PropEditor.dox b/doc/api/PropEditor.dox index 40ce4261..a0bd38a5 100644 --- a/doc/api/PropEditor.dox +++ b/doc/api/PropEditor.dox @@ -73,7 +73,7 @@ A simple example on how to create a property editor and use it with one property list->addProperty("My Group", new Property(String, "Second Property", "This is my second property", "Hello")); list->addProperty(new Property(Color, "Third Property", - "This is my third property", QColor("green"))); + "This is my third property", TQColor("green"))); m_editor->populateProperties(*list); \endcode @@ -88,7 +88,7 @@ More advanced example with property accessors and list intersection: list->addProperty("My Group", new Property(String, "Second Property", "This is my second property", "Hello")); list->addProperty(new Property(Color, "Third Property", - "This is my third property", QColor("green"))); + "This is my third property", TQColor("green"))); PropertyList *list2 = new PropertyList; list2->addProperty("My Group", new Property(Integer, "First Property", -- cgit v1.2.1