🚀 go-pugleaf

Nick B. Cassos wrote:


(snip)

> 
> The main thread (responsible for the GUI) could actually handle it in
> - for example - the OnIdle handler:
> 
> void __fastcall TMainForm::MyIdle(TObject* Sender, bool &Done)
> {
>     if (EventAvailable)
>     {
>         EventAvailable = false;
> 
> 	while (PopEvent())
> 	{
> 	    HandleEvent();
> 	}
>     }
> }
> 
> Of course I am just guessing here, because I do not know the inner
> workings of your thread, how critical it is, etc. I am just proposing
> a way to avoid tighting a worker thread to the main one. If your
> worker thread needs immediate attention then you still could handle
> everything in the "OnEvent" handler * except * any action requiring
> user intervention. If such a case occurs, you could still use the
> above trick. 
> 

Nick,

Maybe the choice of title for this posting is a bit misleading... sorry.

I understand that the solution to this is the use of some "asynchronous" 
process such as OnIdle, or a timer event to get the main thread into the 
message loop before calling the users event handler (which may require 
user intervention).

But I am writing a TComPort class which will be used in half a dozen 
applications. How would I write this into the class? (I am a bit of 
novice when writing classes)

Peter.