🚀 go-pugleaf

"Burak ulutoprak" <bulutoprak@hotmail.com> wrote in message
news:3f27b1dd$1@newsgroups.borland.com...

> ( 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. )

You should stop using MESSAGE_MAPs.  I already explained to you earlier that
they do not work for threads.  Sending messages to threads is not handled
the same way as sending mesages to windows/components.

TThread derives from TObject, which already has a Dispatch() method.  If you
are going to makeshift your own MESSAGE_MAP, then you should name your
dispatching message to something else.

> The problem is I think there is no message queue, so
> the messages coming when processing others are not pooled.

Did you actually create the message queue before trying to use it?  Call
PeekMessage() before entering your while() loop:

    PeekMessage(&msg, NULL, 0, 0, PM_NOREMOVE);


Gambit