hi @BigBen

thats only possible, as long as your long running function does not modify Ui-elements

but yes, QtConcurrent is one of the possible options to use

let me link you to my git repo
https://github.com/DeiVadder/QtThreadExample

that covers all (Qt) ways of parallelisation, and should give you a good starting point

@koahnig said:

Either you need to add "-j4" as make parameter to each of your projects. Otherwise you can set also "MAKEFLAGS=-j4" to your environment (e.g. for a kit as suggested above).

Correction to above post. I have set it to system environment. I did not get it to work in kit environment. Both were set due to my trials, but the latter alone (in kit environment) does not help.

I never tried to start a thread with event loop in a program without main event loop (QApplication). My guess: it will work inside your thread, but you will not be able to communicate with the thread from main thread using signals/slots.

@JKSH
Oh, did not catch that difference. Thank you.

@Varius said:

thread = new QThread(this);
console->moveToThread(thread);

IIRC, these lines are doing more than you think they do. thread's parent is your object, then you move your MyObject instance to thread, so all objects who are child of your MyObject instance are moved the thread. So thread will be moved to itself.

All in all, you should rather have thread in your main as a stack object