TQt4 port kdegames

This enables compilation under both Qt3 and Qt4


git-svn-id: svn://anonsvn.kde.org/home/kde/branches/trinity/kdegames@1236074 283d02a7-25f6-0310-bc7c-ecb5cbfe19da

1 files changed, 57 insertions, 55 deletions

diff --git a/libkdegames/kgame/kmessageserver.h b/libkdegames/kgame/kmessageserver.h
index 3d0b1055..3a416a6b 100644
--- a/libkdegames/kgame/kmessageserver.h
+++ b/libkdegames/kgame/kmessageserver.h
@@ -73,53 +73,53 @@ class KMessageServerPrivate;
 
   Here is a list of the messages the KMessageServer understands:
   << means, the value is inserted into the TQByteArray using TQDataStream. The
-  messageIDs (REQ_BROADCAST, ...) are of type Q_UINT32.
+  messageIDs (RETQ_BROADCAST, ...) are of type TQ_UINT32.
 
-  - TQByteArray << static_cast&lt;Q_UINT32>( REQ_BROADCAST ) << raw_data
+  - TQByteArray << static_cast&lt;TQ_UINT32>( RETQ_BROADCAST ) << raw_data
 
     When the server receives this message, it sends the following message to
     ALL connected clients (a broadcast), where the raw_data is left unchanged:
-       TQByteArray << static_cast &lt;Q_UINT32>( MSG_BROADCAST ) << clientID << raw_data
-       Q_UINT32 clientID; // the ID of the client that sent the broadcast request
+       TQByteArray << static_cast &lt;TQ_UINT32>( MSG_BROADCAST ) << clientID << raw_data
+       TQ_UINT32 clientID; // the ID of the client that sent the broadcast request
 
-  - TQByteArray << static_cast&lt;Q_UINT32>( REQ_FORWARD ) << client_list << raw_data
-    TQValueList &lt;Q_UINT32> client_list; // list of receivers
+  - TQByteArray << static_cast&lt;TQ_UINT32>( RETQ_FORWARD ) << client_list << raw_data
+    TQValueList &lt;TQ_UINT32> client_list; // list of tqreceivers
 
     When the server receives this message, it sends the following message to
     the clients in client_list:
-        TQByteArray << static_cast&lt;Q_UINT32>( MSG_FORWARD ) << senderID << client_list << raw_data
-        Q_UINT32 senderID;  // the sender of the forward request
-        TQValueList &lt;Q_UINT32> client_list; // a copy of the receiver list
+        TQByteArray << static_cast&lt;TQ_UINT32>( MSG_FORWARD ) << senderID << client_list << raw_data
+        TQ_UINT32 senderID;  // the sender of the forward request
+        TQValueList &lt;TQ_UINT32> client_list; // a copy of the receiver list
 
     Note: Every client receives the message as many times as he is in the client_list.
     Note: Since the client_list is sent to all the clients, every client can see who else
-          got the message. If you want to prevent this, send a single REQ_FORWARD
+          got the message. If you want to prevent this, send a single RETQ_FORWARD
           message for every receiver.
 
-  - TQByteArray << static_cast&lt;Q_UINT32>( REQ_CLIENT_ID )
+  - TQByteArray << static_cast&lt;TQ_UINT32>( RETQ_CLIENT_ID )
 
     When the server receives this message, it sends the following message to
     the asking client:
-        TQByteArray << static_cast&lt;Q_UINT32>( ANS_CLIENT_ID ) << clientID
-        Q_UINT32 clientID;  // The ID of the client who asked for it
+        TQByteArray << static_cast&lt;TQ_UINT32>( ANS_CLIENT_ID ) << clientID
+        TQ_UINT32 clientID;  // The ID of the client who asked for it
 
     Note: This answer is also automatically sent to a new connected client, so that he
           can store his ID. The ID of a client doesn't change during his lifetime, and is
           unique for this KMessageServer.
 
-  - TQByteArray << static_cast&lt;Q_UINT32>( REQ_ADMIN_ID )
+  - TQByteArray << static_cast&lt;TQ_UINT32>( RETQ_ADMIN_ID )
 
     When the server receives this message, it sends the following message to
     the asking client:
         TQByteArray << ANS_ADMIN_ID << adminID
-        Q_UINT32 adminID;  // The ID of the admin
+        TQ_UINT32 adminID;  // The ID of the admin
 
     Note: This answer is also automatically sent to a new connected client, so that he
           can see if he is the admin or not. It will also be sent to all connected clients
-          when a new admin is set (see REQ_ADMIN_CHANGE).
+          when a new admin is set (see RETQ_ADMIN_CHANGE).
 
-  - TQByteArray << static_cast&lt;Q_UINT32>( REQ_ADMIN_CHANGE ) << new_admin
-    Q_UINT32 new_admin;  // the ID of the new admin, or 0 for no admin
+  - TQByteArray << static_cast&lt;TQ_UINT32>( RETQ_ADMIN_CHANGE ) << new_admin
+    TQ_UINT32 new_admin;  // the ID of the new admin, or 0 for no admin
 
     When the server receives this message, it sets the admin to the new ID. If no client
     with that ID exists, nothing happens. With new_admin == 0 no client is a admin.
@@ -127,8 +127,8 @@ class KMessageServerPrivate;
 
     Note: The server sends a ANS_ADMIN_ID message to every connected client.
 
-  - TQByteArray << static_cast&lt;Q_UINT32>( REQ_REMOVE_CLIENT ) << client_list
-    TQValueList &lt;Q_UINT32> client_list; // The list of clients to be removed
+  - TQByteArray << static_cast&lt;TQ_UINT32>( RETQ_REMOVE_CLIENT ) << client_list
+    TQValueList &lt;TQ_UINT32> client_list; // The list of clients to be removed
 
     When the server receives this message, it removes the clients with the ids stored in
     client_list, disconnecting the connection to them.
@@ -137,22 +137,22 @@ class KMessageServerPrivate;
     Note: If one of the clients is the admin himself, he will also be deleted.
           Another client (if any left) will become the new admin.
 
-  - TQByteArray << static_cast&lt;Q_UINT32>( REQ_MAX_NUM_CLIENTS ) << maximum_clients
-    Q_INT32 maximum_clients; // The maximum of clients connected, or infinite if -1
+  - TQByteArray << static_cast&lt;TQ_UINT32>( RETQ_MAX_NUM_CLIENTS ) << maximum_clients
+    TQ_INT32 maximum_clients; // The maximum of clients connected, or infinite if -1
 
     When the server receives this message, it limits the number of clients to the number given,
     or sets it unlimited for maximum_clients == -1.
     ONLY THE ADMIN CAN USE THIS MESSAGE!
 
     Note: If there are already more clients, they are not affected. It only prevents new Clients
-          to be added. To assure this limit, remove clients afterwards (REQ_REMOVE_CLIENT)
+          to be added. To assure this limit, remove clients afterwards (RETQ_REMOVE_CLIENT)
 
-  - TQByteArray  << static_cast&lt;Q_UINT32>( REQ_CLIENT_LIST )
+  - TQByteArray  << static_cast&lt;TQ_UINT32>( RETQ_CLIENT_LIST )
 
     When the server receives this message, it answers by sending a list of IDs of all the clients
     that are connected at the moment. So it sends the following message to the asking client:
-        TQByteArray << static_cast&lt;Q_UINT32>( ANS_CLIENT_LIST ) << clientList
-        TQValueList &lt;Q_UINT32> clientList;  // The IDs of the connected clients
+        TQByteArray << static_cast&lt;TQ_UINT32>( ANS_CLIENT_LIST ) << clientList
+        TQValueList &lt;TQ_UINT32> clientList;  // The IDs of the connected clients
 
     Note: This message is also sent to every new connected client, so that he knows the other
           clients.
@@ -160,36 +160,37 @@ class KMessageServerPrivate;
   There are two more messages that are sent from the server to the every client automatically
   when a new client connects or a connection to a client is lost:
 
-        TQByteArray << static_cast&lt;Q_UINT32>( EVNT_CLIENT_CONNECTED ) << clientID;
-        Q_UINT32 clientID;   // the ID of the new connected client
+        TQByteArray << static_cast&lt;TQ_UINT32>( EVNT_CLIENT_CONNECTED ) << clientID;
+        TQ_UINT32 clientID;   // the ID of the new connected client
 
-        TQByteArray << static_cast&lt;Q_UINT32>( EVNT_CLIENT_DISCONNECTED ) << clientID;
-        Q_UINT32 clientID;   // the ID of the client that lost the connection
-        Q_UINT8 broken;      // 1 if the network connection was closed, 0 if it was disconnected
+        TQByteArray << static_cast&lt;TQ_UINT32>( EVNT_CLIENT_DISCONNECTED ) << clientID;
+        TQ_UINT32 clientID;   // the ID of the client that lost the connection
+        TQ_UINT8 broken;      // 1 if the network connection was closed, 0 if it was disconnected
                              // on purpose
 
 
   @author Andreas Beckermann <b_mann@gmx.de>, Burkhard Lehner <Burkhard.Lehner@gmx.de>
   @version $Id$
 */
-class KMessageServer : public QObject
+class KMessageServer : public TQObject
 {
   Q_OBJECT
+  TQ_OBJECT
 
 public:
     /**
       MessageIDs for messages from a client to the message server.
     */
     enum { 
-            REQ_BROADCAST = 1, 
-            REQ_FORWARD,
-            REQ_CLIENT_ID,
-            REQ_ADMIN_ID,
-            REQ_ADMIN_CHANGE,
-            REQ_REMOVE_CLIENT,
-            REQ_MAX_NUM_CLIENTS,
-            REQ_CLIENT_LIST,
-            REQ_MAX_REQ = 0xffff };
+            RETQ_BROADCAST = 1, 
+            RETQ_FORWARD,
+            RETQ_CLIENT_ID,
+            RETQ_ADMIN_ID,
+            RETQ_ADMIN_CHANGE,
+            RETQ_REMOVE_CLIENT,
+            RETQ_MAX_NUM_CLIENTS,
+            RETQ_CLIENT_LIST,
+            RETQ_MAX_REQ = 0xffff };
 
     /**
      * MessageIDs for messages from the message server to a client.
@@ -208,7 +209,7 @@ public:
     /**
      * Create a KGameNetwork object
      **/
-    KMessageServer(Q_UINT16 cookie = 42, TQObject* parent = 0);
+    KMessageServer(TQ_UINT16 cookie = 42, TQObject* tqparent = 0);
 
     ~KMessageServer();
 
@@ -226,7 +227,7 @@ public:
      * system pick a free port
      * @return true if it worked
     */
-    bool initNetwork (Q_UINT16 port = 0);
+    bool initNetwork (TQ_UINT16 port = 0);
 
     /**
      * Returns the TCP/IP port number we are listening to for incoming connections.
@@ -234,7 +235,7 @@ public:
      * especially necessary if you used 0 as port number in initNetwork().
      * @return the port number
      **/
-    Q_UINT16 serverPort () const;
+    TQ_UINT16 serverPort () const;
 
     /**
      * Stops listening for connections. The already running connections are
@@ -325,14 +326,14 @@ public:
     /**
      * returns a list of the unique IDs of all clients.
      **/
-    TQValueList <Q_UINT32> clientIDs() const;
+    TQValueList <TQ_UINT32> clientIDs() const;
 
     /**
      * Find the @ref KMessageIO object to the given client number.
      * @param no the client number to look for, or 0 to look for the admin
      * @return address of the client, or 0 if no client with that number exists
      **/
-    KMessageIO *findClient (Q_UINT32 no) const;
+    KMessageIO *findClient (TQ_UINT32 no) const;
 
     /**
      * Returns the clientID of the admin, if there is a admin, 0 otherwise.
@@ -340,14 +341,14 @@ public:
      * NOTE: Most often you don't need to know that id, since you can
      * use clientID 0 to specify the admin.
      **/
-    Q_UINT32 adminID() const;
+    TQ_UINT32 adminID() const;
 
     /**
      * Sets the admin to a new client with the given ID.
      * The old admin (if existed) and the new admin will get the ANS_ADMIN message.
      * If you use 0 as new adminID, no client will be admin.
      **/
-    void setAdmin (Q_UINT32 adminID);
+    void setAdmin (TQ_UINT32 adminID);
 
 
 //------------------------------ ID stuff
@@ -385,7 +386,7 @@ public:
      * @ref findClient (id)->send(msg) manually, but this method checks for
      * errors.
      **/
-    virtual void sendMessage (Q_UINT32 id, const TQByteArray &msg);
+    virtual void sendMessage (TQ_UINT32 id, const TQByteArray &msg);
 
     /**
      * Sends a message to a list of clients. Their ID is given in ids. If
@@ -394,7 +395,7 @@ public:
      * This is just a convenience method. You could also iterate over the
      * list of IDs.
      **/
-    virtual void sendMessage (const TQValueList <Q_UINT32> &ids, const TQByteArray &msg);
+    virtual void sendMessage (const TQValueList <TQ_UINT32> &ids, const TQByteArray &msg);
 
 protected slots:
     /**
@@ -448,7 +449,7 @@ signals:
      * @param clientID the ID of the KMessageIO object that received the message
      * @param unknown true, if the message type is not known by the KMessageServer
      **/
-    void messageReceived (const TQByteArray &data, Q_UINT32 clientID, bool &unknown);
+    void messageReceived (const TQByteArray &data, TQ_UINT32 clientID, bool &unknown);
 
 protected:
     /**
@@ -456,7 +457,7 @@ protected:
      * incremented after every call so if you need the id twice you have to save
      * it anywhere. It's currently used to initialize newly connected clints only.
      **/
-    Q_UINT32 uniqueClientNumber() const;
+    TQ_UINT32 uniqueClientNumber() const;
 
 private:
     KMessageServerPrivate* d;
@@ -468,17 +469,18 @@ private:
   connections.
 
   NOTE: This has to be here in the header file, because it is a subclass from
-  TQObject and has to go through the moc.
+  TQObject and has to go through the tqmoc.
 
   @short An internal class for KServerSocket
   @author Burkhard Lehner <Burkhard.Lehner@gmx.de>
 */
-class KMessageServerSocket : public QServerSocket
+class KMessageServerSocket : public TQServerSocket
 {
   Q_OBJECT
+  TQ_OBJECT
 
 public:
-  KMessageServerSocket (Q_UINT16 port, TQObject *parent = 0);
+  KMessageServerSocket (TQ_UINT16 port, TQObject *tqparent = 0);
   ~KMessageServerSocket ();
 
   void newConnection (int socket);