🚀 go-pugleaf

"Paul at NCF" <notplmacca@clara.co.uk> wrote in message 
news:45de1d0f@newsgroups.borland.com...
>
> I may have lost the plot, but I thought you wanted to pass information to 
> a (secondary) thread from the main VCL thread (mainform)?

Yes.

> So the VCL thread is adding to the queue.

Yes.

> The thread could then get signaled and woken up, and remove the item off 
> the queue.

Yes.  That's what the HandleCommand is there for, and why it's in the 
sctpThread.


> Not sure it did.  Looked to me like the VCL thread added the command to 
> the queue, and then calls the threads handle command to take it off the 
> queue and process it?

Isn't that what you just said it should do?


> WaitForMultipleObjects would only wake up the thread when something was 
> signalled.  And it would only block the VCL thread when it was locked

But I can't have the thread sleeping or waiting or anything else that would 
keep it from processing the library's event loop.  It might be a while 
before the next time the main unit initiates an outgoing message, but in the 
meantime, the library still needs to keep looking for incoming messages.  It 
relies on sctp_eventLoop() being called continuously.  Whatever I add into 
the Execute's while loop has to co-exist peacefully with:

    while (! Terminated ) {
     if (sctp_eventLoop() < 0)
       break ;
    }

and not block that eventLoop from happening.