Re: [Dev-C++] window procedures and threads

[<or...@vp...>]

OROSZI Bal=E1zs wrote:
> I have a question regarding window procedures.
> I have a normal windows application, which at some point displays a=20
> modeless dialog box. That is, I have to press OK or CANCEL to return to=
=20
> my app, and the execution of the code is "supposedly" blocked. BUT: If =
I=20
> move around the dialog box, I can clearly see, that the window=20
> underneath (my main window) is actually getting paint messages, that is=
,=20
> it's window procedure is called.
> Now, my question is: while my dialog box is displayed, does windows=20
> automatically create a new thread for calling the window procedure, or=20
> is it called from the same thread, as the dialog box's? But then how? A=
s=20
> the code is supposedly blocked, until I close the dialog.

It seems I have found the answer for this, so I'll just reply to myself i=
n case anyone's=20
browsing this in the archives.
The MS docs say, that there are certain messages (or situations), when th=
e window=20
procedure is called directly, bypassing the message loop. It is described=
 in the "Messages=20
and Message Queues" section (under "Nonqueued Messages" title) of the win=
32 API docs, so=20
look there for details.

--
Greetings,
   Bal=E1zs