Thank you @SGaist ! I figured it was something along those lines but couldn't put my finger on it.

Process still block, when I lost connection.

Hi @Sebastien-Leon and welcome to devnet, Can you post the link to the bug report / gerrit review you made ?

@enjoysmath I wouldn't expect to need to use that, and would have thought it could lead to other problems. A dialog should be on top anyway. Did you try just passing the main window as the parent?

@danividanivi Ok super. To sleep good at night, i think i would check that correct widget have focus before sending enter to avoid some day it might find the close dialog button or something later on :)

@oblivioncth said: Ok, its shaping up , super :) "Helps givez me codes". We do help those too but good questions often get better answers. Also its clear that you do try to fix it first yourself, so some holes in c++ is no issue. Cheers

@Chris-Kawa said: QThread docs Oh!! Then I need to make a worker class and do something like: thread = new QThread(); thread->start(); worker = new Worker; worker->moveToThread(thread); // this is the initialization of a QWizardPage in the QWizard WizardPageClass1 *page1 = new WizardPageClass1 ; page1->setWorker(worker); And then where I have the lengthy operation, emit a signal (DoOperation for example) and in its constructor make a connect like connect(this, DoOperation(), worker, doWork()) if doWork() is where I have the lenghty operation with?

You have to place the respective libraries and plugins in corresponding place where the executable is placed. And the libraries and plugins must be refering to executables.

My understanding of self.close() got the better of me. self.close() returns self.reject(). That was what I did not understand. self.done(1) would also work, but I think self.accept() is clearer in this case. Thank you QT-static-prgm.

@Chris-Kawa Oh wow. I didn't even know about that! Thanks! :D