Guess: The nature of the signal slot is implemented using Windows custom messages

In continuous execution:

void Mytool::D eleteallfiles ()
{
for (i = 0; I <= n-1; i++) {
Do something
}
}
In the case where the for loop is not completed, the external signal to this class is not received at all. It has to be written like this:

void Mytool::D eleteallfiles ()
{
for (i = 0; I <= n-1; i++) {
Qapplication::p rocessevents ();
Do something
}
}
Or:
void Mytool::D eleteallfiles ()
{
Qeventloop Loop;
for (i = 0; I <= n-1; i++) {
Loop.processevents ();
Do something
}
}
This ensures that the queue signal can be received in time and the slot function is triggered. But the familiar style, I can only doubt the nature of the signal slot is the Windows message mechanism ....

Http://www.qtcn.org/bbs/read-htm-tid-62003-ds-1-page-1.html

Guess: The nature of the signal slot is implemented using Windows custom messages