🚀 go-pugleaf

Hi,i have a problem with messages and threads.I am using threads which are
communicating between each other by sending messages. The handling of
messages is like that.
while(1)
 while( (bRet = GetMessage( &msg, NULL, 0, 0 )) != 0)
{
              Dispatch(&msg);
}



( I change the definition of BEGIN_MESSAGE_MAP to
#define MY_BEGIN_MESSAGE_MAP virtual void __fastcall Dispatch(tagMSG
*Message) { switch  (Message->message)    {
which causes problem with threads and I have no problem with that part. )


Here when GetMessage takes a message, dispatch function cannot return
immidiately, becaouse message handling functions need user intraction in
order to return ,which causes dispatch method to return very late. So when
GetMessage function looks for another message , it does not return even if
more messages are sent. Only  messages after GetMessage Function is invoked
can be handled.
The problem is I think there is no message queue, so the messages coming
when processing others are not pooled.
I know that PeekMessage functions return true for lost messages.

Win32 SDK says that
 "all threads are created initially without a message queue. The system
creates a thread's message queue only when the thread makes its first call
to one of the Win32 API User or GDI functions."
So does first call to GetMessage function creates a message queue. If yes
why I lose messages caming in handling period, if no how can I create a
message queue for a thread.

Thanks for help