QThread usage and exec()

[smahnken]

I guess I'm not expert enough to say that I'm certain, but I'm pretty sure. Perhaps you can provide a sanity check for me...

The server class is declared like so:

class Xorbz_Game : public QThread
{
   Q_OBJECT
 
   public:
      Xorbz_Game( class Xorbz* parent );
      ~Xorbz_Game( void );

class Xorbz_Game : public QThread
{
   Q_OBJECT

   public:
      Xorbz_Game( class Xorbz* parent );
      ~Xorbz_Game( void );

To copy to clipboard, switch view to plain text mode 

etc...

The client (main app) instantiates the server like so:

// Instantiate a new game engine
   currentGame = new Xorbz_Game( this );

// Instantiate a new game engine
   currentGame = new Xorbz_Game( this );

To copy to clipboard, switch view to plain text mode 

After the client sets a few things in the server via member functions, it starts things up like this:

// Start the game running
      currentGame->start();

// Start the game running
      currentGame->start();

To copy to clipboard, switch view to plain text mode 

Anything look amiss?

[jacek]

Anything look amiss?

No, you must block the main event loop in some other way. Do you have any loops in your GUI code?

[smahnken]

No loops in my GUI code, but maybe I'm chasing the wrong thing. I'm probably doing something wrong with the graphics. I found that if I resize the window, or minimize/restore it, the graphics do update, but only while I'm resizing.

The whole project is a migration effort from the QT 3.x series, in which the code base used the QCanvas and QPixmapArray stuff. I'm now trying to establish the same functionality with the QT 4.x series.

I'll go poke around (and read) some more with the new graphics structure. I know there's the whole update() thing, but there's a good chance I've got something wrong there. I'll start a new discussion thread once I've got some substantiated questions.

Thanks again for your help!

[wysota]

Are you sure you need threads at all?