how to resume QThread::wait()?

[high_flyer]

If you want your object to work sequentially, (you wait for each obj to finish before you start the next) then what do you need a thread for?
Lets say, its because the work done on each object is long, and you want the GUI responsive - ok.
On way is to get rid of the wait, and have a "thread starter" slot connected to the finished() signal of the threads, and then you can start the next.

But it looks to me you are trying to force using threads where they are not really needed, and that a proper design would simplify the whole thing dramatically.

[naturalpsychic]

thanks for reply

But it looks to me you are trying to force using threads where they are not really needed, and that a proper design would simplify the whole thing dramatically.

Yes you are right, i am trying to force using thread but it is needed at the same time, because of the same reason you mentioned, to keep my GUI responsive, without having threads my GUI will just go unresponsive.

On way is to get rid of the wait, and have a "thread starter" slot connected to the finished() signal of the threads, and then you can start the next.

i think you meant by:

cObj->connect(&thread,SIGNAL(started()),SLOT(show()));
 thread.connect(&thread,SIGNAL(finished()),&thread,SLOT(start()));
 
 
 thread.start();
 //thread.wait();       //COMMENTED THIS OUT

cObj->connect(&thread,SIGNAL(started()),SLOT(show()));
 thread.connect(&thread,SIGNAL(finished()),&thread,SLOT(start()));


 thread.start();
 //thread.wait();       //COMMENTED THIS OUT

To copy to clipboard, switch view to plain text mode 

but obviously it wont work either because none of thread is waiting to finish...and if i uncomment above thread.wait() then execution of thread never finishes to start next one, i mean finished() signal is never emitted from &thread obj.

[high_flyer]

There are all kinds of problems in what you are saying...
But I'll start from the end:
If you have some work that needs to be done out side the GUI thread, and that work has to be sequential, then why do you put all the stages in different threads?
Have one thread call the stages one aftter the other, instead of putting each stage in its own thread.
So something like:
1. Have your thread object take a list of the objects.
2. In run() iterate over the list and call the work functions on the objects.
3. In the gui thread just have your one worker thread notify you when it is finished.