🚀 go-pugleaf

    MsgWaitForMultipleObjects is used only when you are waiting an message
and an synchronizable object to be signaled.
    If you don't have synchronizable object to wait don't use
MsgWaitForMultipleObjects.

    Tales Aguiar.

"tinyabs" <nospam@me.com> wrote in message
news:42f8844e@newsgroups.borland.com...
>
> "Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message
> news:42f78d85$4@newsgroups.borland.com...
> >
> > "tinyabs" <nospam@me.com> wrote in message
> > news:42f705fd@newsgroups.borland.com...
> >
> >> I'm interested to know whether I can override the default message loop.
> >
> > That depends on whether you are using the VCL are not.  If so, then no.
> > TApplication::Run() is required as it does things internally that you do
> > not
> > have access to.
> >
> > What EXACTLY do you want to accomplish?
> >
> >> I'm trying to use MsgWaitForMultipleObjects() in my application.
> >
> > What does that have to do with overriding the message loop?
> >
> >
> > Gambit
> >
> >
> I had a pipe client communicating with a service app. I'm redirecting pipe
> byte messages into the WndProc as WM events. Currently, I use
PostMessage()
> and pipe->GetMessage() to redirect the pipe messages.
>
>