Replace QObject, QWidget, QImage, QPair, QRgb, QColor, QChar, QString, QIODevice with TQ* version

Signed-off-by: Michele Calgaro <[email protected]>
(cherry picked from commit 3d786f111190b8bbce1f0b572acc85b5a9da967c)

3 files changed, 10 insertions, 10 deletions

diff --git a/acinclude.m4 b/acinclude.m4
index 18c1b433..2db09a62 100644
--- a/acinclude.m4
+++ b/acinclude.m4
@@ -1133,14 +1133,14 @@ cat >> conftest.$ac_ext <<EOF
 EOF
 if test $kde_qtsubver -gt 0; then
 cat >> conftest.$ac_ext <<EOF
-    QString s;
+    TQString s;
     s.setLatin1("Elvis is alive", 14);
 EOF
 fi
 fi
 if test "$kde_qtver" = "3"; then
 cat >> conftest.$ac_ext <<EOF
-    (void)QStyleFactory::create(QString::null);
+    (void)QStyleFactory::create(TQString::null);
     QCursor c(Qt::WhatsThisCursor);
 EOF
 fi
@@ -4690,7 +4690,7 @@ AC_TRY_RUN(dnl
 #include <qimageio.h>
 #include <qstring.h>
 int main() {
-		QString t = "hallo";
+		TQString t = "hallo";
 		t.fill('t');
 		qInitImageIO();
 }
diff --git a/digikam/libs/dimg/README b/digikam/libs/dimg/README
index 8b79bdef..47e4a4ce 100644
--- a/digikam/libs/dimg/README
+++ b/digikam/libs/dimg/README
@@ -23,7 +23,7 @@ support for them. so the only solution  I see (without depending on
 imagemagick) is to roll our own library.
 
 i have been working on a imaging library for digikam, its called DImg. 
-it doesn't aim to be a complete imaging library; it uses QImage for 
+it doesn't aim to be a complete imaging library; it uses TQImage for 
 rendering and for loading files which are not supported natively by it. 
 some of the working/planned features:
 
@@ -53,11 +53,11 @@ scale (this has been ported from Imlib2 - originally ported by Mosfet, I
 added 16 bit scaling support and support for scaling of only a section of 
 the image)
 
-* Rendering to Pixmap: using QImage/QPixmap. (see above for rendering of 
+* Rendering to Pixmap: using TQImage/QPixmap. (see above for rendering of 
 16bit images).
 
-* Pixel format: the pixel format is different from QImage/Imlib2 pixel 
-format. In QImage/Imlib2 the pixel data is stored as unsigned ints and to 
+* Pixel format: the pixel format is different from TQImage/Imlib2 pixel 
+format. In TQImage/Imlib2 the pixel data is stored as unsigned ints and to 
 access the individual colors you need to use bit-shifting to ensure 
 endian correctness. in DImg, the pixel data is stored as unsigned char. 
 the color layout is B,G,R,A (blue, green, red, alpha)
@@ -89,7 +89,7 @@ for (int i=0; i<image.width()*image.height(); i++)
 }
 
 the above is true for both big and little endian platforms. What this also 
-means is that the pixel format is different from that of QImage for big 
+means is that the pixel format is different from that of TQImage for big 
 endian machines. Functions are provided if you want to get a copy of the 
-DImg as a QImage.
+DImg as a TQImage.
 
diff --git a/digikam/libs/dimg/loaders/README b/digikam/libs/dimg/loaders/README
index e3a8c60d..b77e9c4c 100644
--- a/digikam/libs/dimg/loaders/README
+++ b/digikam/libs/dimg/loaders/README
@@ -11,7 +11,7 @@ RAW     Done  N.A    N.A   Done      Done    yes      yes     dcraw      Metadat
 PPM     Done  TODO   N.A   N.A       N.A     yes      yes     none
 JPEG2K  Done  Done   Done  TODO      N.A     yes      yes     libjasper  Metadata are EXIF/XMP/ICC profil
 
-Others file formats are supported only in 8 bits/color/pixel using QImage/kimgio. 
+Others file formats are supported only in 8 bits/color/pixel using TQImage/kimgio. 
 QT3.x + KDE 3.4.x support these formats :
 
 Format   Read       Write      Remarks