🚀 go-pugleaf

Remy Lebeau (TeamB) wrote:

>"Belongs" is not the best term to use. 

It was the best I could come up with. The callback is bound to the
function for the duration of the function. It is not an exclusive
binding (others may also bind to it), but it cannot be replaced during
the execution of the function (there might be some exceptions, but
that would be dirty code wouldn't it?).

>> Your MainWndProc is a subroutine of DispatchMessage,
>> and belongs to the thread/process that calls it.
>
>See above.  In the case of a window procedure, it is always called by the
>thread that creates the window.  DispatchMessage() is not the only way that
>a window procedure gets called.  SendMessage() can call a window procedure
>directly.

Doesn't sound like it..Sounds more like it places a message in the
original thead's queue, and the original thread's DispatchMessage
calls the callback. Otherwise, the original thead could be doing 2
things at the same time.
Doesn't SendMessage have to wait it's turn just like all the other
messages?

>  If SendMessage() is called from a different thread, Windows
>switches to the thread that owns the window and then that thread calls the
>window procedure.

So the owner thead calls it through DispatchMessage?