Make ui stay responsive when executin thread

[aguleo]

I subclassed QThread and it's run method like this:

mythread.h


#ifndef MYTHREAD_H
#define MYTHREAD_H

#include <QThread>
#include <QString>

class myThread : public QThread
{
Q_OBJECT
public:
myThread();
void run();

private:
//...
};

#endif // MYTHREAD_H


mythread.cpp


#include "mythread.h"
#include <iostream>

myThread::myThread()
{
//...
}

void myThread::run()
{
for(int i=0; i<10; i++)
{
QThread::sleep(1);
std::cout << i << std::endl;
}
}


How and when can i call this thread in order que keep the application responsive?

Sorry if it makes no sense ... my first thread experience :)

[Santosh Reddy]

How and when can i call this thread in order que keep the application responsive?
It doesn't matter, whenever you want...:)

[aguleo]

How is that?
i'm calling it from QMainWindow and i have to wait 10 seconds before i hava access to the menu again!

[wysota]

i'm calling it
"It", being what exactly?

[aguleo]

I attach "it" :)
I guess i can not call it from that member ... isn't it?

[Santosh Reddy]

How is that?
i'm calling it from QMainWindow and i have to wait 10 seconds before i hava access to the menu again!
No it won't wait, (That is whats Thread's do)

To run the thread you should be calling QThread::start() (not QThread::run()), this will run the thread in it own (new thread) context

If you call QThread::run(), it will execute in the calling thread context.

[aguleo]

Ok ... made some progress.
I was creating the thread inside a member function ... this way it ended unexpectedly ...
But now i have a question. What happens when i call the same option again while it is still running?
I ask because apparently nothing does!

[Santosh Reddy]

But now i have a question. What happens when i call the same option again while it is still running?
If the thread is running, then nothing will happen.
If the thread is not running, the thread will start running, provided all waiting conditions are cleared.

[lightydo]

if you want to run another thread instance, then create an array of threads and run them as you require. don't forget to capture their ending event so you know which are running.
if you need to synchronize concurrent access to shared item, conside QSharedMemory or QSempahore.

[wysota]

Maybe you should first tell us what you want the thread to do?

[aguleo]

There was nothing specific on my mind. I read something about saving large files to disk in the "C++ GUI programming with Qt4" and got curiouse.

Maybe you should first tell us what you want the thread to do?
You mean that the approach will depend on what i want to do ... is it so?

[wysota]

Yes, for many usecases using a thread is either not possible or simply bad idea.

Here, read this: Keeping the GUI Responsive