@JackMyson
You don't actually show the message box being shown (exec()?). Nothing special here. Try not subclassing the QMessageBox and using that directly, so you can rule that out. Try a standalone application without anything of your own. Try passing nullptr as parent to the constructor, any difference? Are you sure you are not using Wayland rather than Xorg, that might make its position or behaviour different.

Well, Qt has both a QMenu and a QMenuItem. Only the QMenuItem is supposed to trigger actions. The QMenu itself only has QMenuItems and submenus. So, its action is already defined.

Usually, the QMenuItems have QActions associated with it. For the QMenu::triggered signal the documentation states:

This signal is emitted when an action in this menu is triggered.

To me this reads that you have several entries inside the QMenu and one of these entries triggers an action. This is also why this signal contains the QAction as a parameter. My understanding would mean that clicking on the QMenu itself does not emit a triggered signal, but only clicking on a QMenuItem does.

Thanks @Bonnie, You are AWESOME!

Glad you found out !

Could you explain what happened in your code to trigger this ?

@joeQ As it turns out, I just tried the opposite. I had one newed Message Box for everything. In the place that had the funny location, I made a separate newed Message Box and it ended up in the correct place - the middle of its parent.

Yes, i've found how to change the text

Thank you.

@jsulm

pbar is in the VBoxLayout of the dialog, q is a QSqlQuery.

I Just modified the code so that the dialog also contains the yes and no buttons and no QMessageBox is shown. When i now show the QDialog instead of the QMessageBox and then execute the slot, everything looks good and the progressbar is updated at each step of the foreach() loop.

@Harry123
I did it putting this in main.cpp and that's all folks ;-)

QApplication a(argc, argv); a.setStyle("fusion");

@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?