summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMichele Calgaro <michele.calgaro@yahoo.it>2023-09-23 12:44:34 +0900
committerMichele Calgaro <michele.calgaro@yahoo.it>2023-09-25 12:26:28 +0900
commite5e8e3221561c92ace9e485a3b8778da1e4b5fbb (patch)
treee1e83d02ec6997a200b37d56e11815ee79146bae
parent06dd1557e7112a3965f7ea777e149fcb0a10b630 (diff)
downloadtdemultimedia-e5e8e3221561c92ace9e485a3b8778da1e4b5fbb.tar.gz
tdemultimedia-e5e8e3221561c92ace9e485a3b8778da1e4b5fbb.zip
Replace QObject, QWidget, QImage, QPair, QRgb, QColor, QChar, QString, QIODevice with TQ* version
Signed-off-by: Michele Calgaro <michele.calgaro@yahoo.it> (cherry picked from commit 938578ffc3e80f59646041c2483985f1d70692f6)
-rw-r--r--doc/artsbuilder/detail.docbook2
-rw-r--r--doc/artsbuilder/mcop.docbook4
-rw-r--r--noatun/modules/making_plugins2
3 files changed, 4 insertions, 4 deletions
diff --git a/doc/artsbuilder/detail.docbook b/doc/artsbuilder/detail.docbook
index 34adf3d1..37d5e328 100644
--- a/doc/artsbuilder/detail.docbook
+++ b/doc/artsbuilder/detail.docbook
@@ -1415,7 +1415,7 @@ once you assigned something else (like a null reference).
<para>
The equivalent C++ terms would be
<programlisting>
- QWidget* w;
+ TQWidget* w;
w-&gt;show();
</programlisting>
diff --git a/doc/artsbuilder/mcop.docbook b/doc/artsbuilder/mcop.docbook
index 4b1d6615..ca4a195a 100644
--- a/doc/artsbuilder/mcop.docbook
+++ b/doc/artsbuilder/mcop.docbook
@@ -2197,11 +2197,11 @@ that, I am certainly proven wrong.
While I do know that &DCOP; basically doesn't know about the data types
it sends, so that you could use &DCOP; without using &Qt;, look at how
it is used in daily &kde; usage: people send types like
-<classname>QString</classname>, <classname>QRect</classname>,
+<classname>TQString</classname>, <classname>QRect</classname>,
<classname>QPixmap</classname>, <classname>QCString</classname>, ...,
around. These use &Qt;-serialization. So if somebody choose to support
&DCOP; in a GNOME program, they would either have to claim to use
-<classname>QString</classname>,... types (although they don't do so),
+<classname>TQString</classname>,... types (although they don't do so),
and emulate the way &Qt; does the streaming, or they would send other
string, pixmap and rect types around, and thus not be interoperable.
</para>
diff --git a/noatun/modules/making_plugins b/noatun/modules/making_plugins
index cb921cc2..0134b321 100644
--- a/noatun/modules/making_plugins
+++ b/noatun/modules/making_plugins
@@ -6,7 +6,7 @@ You're free to use the net plugin as a base, I've licensed it under the
public domain, so you can relicense it however you wish (preferably not
GPL, though :)
-Remember that QObject must derive first.
+Remember that TQObject must derive first.
Do a "return this;" in the PlayList *playlist() const; function, if your class
is a playlist, otherwise, don't even override that function.