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 241e0082f7b9ccadaeed0ef43a1c9ebb9b4fe840)

1 files changed, 1 insertions, 1 deletions

diff --git a/tde-i18n-de/docs/tdemultimedia/artsbuilder/detail.docbook b/tde-i18n-de/docs/tdemultimedia/artsbuilder/detail.docbook
index dc874b70bbe..075e1770ee9 100644
--- a/tde-i18n-de/docs/tdemultimedia/artsbuilder/detail.docbook
+++ b/tde-i18n-de/docs/tdemultimedia/artsbuilder/detail.docbook
@@ -562,7 +562,7 @@ public:
    Arts::Synth_PLAY p;
    string s = p.toString();
 </programlisting> <para> is something different than dereferencing a NULL pointer. You didn't tell the object at all what it is, and now you try to use it. The guess here is that you want to have a new local instance of a Arts::Synth_PLAY object. Of course you might have wanted something else (like creating the object somewhere else, or using an existing remote object). However, it is a convenient short cut to creating objects. Lazy creation will not work once you assigned something else (like a null reference). </para> <para> The equivalent C++ terms would be <programlisting>
-   QWidget* w;
+   TQWidget* w;
    w-&gt;show();
 </programlisting> which obviously in C++ just plain segfaults. So this is different here. This lazy creation is tricky especially as not necessarily an implementation exists for your interface. </para> <para> For instance, consider an abstract thing like a Arts::PlayObject. There are certainly concrete PlayObjects like those for playing mp3s or wavs, but <programlisting>
    Arts::PlayObject po;