🚀 go-pugleaf

On Wed, 28 May 2003 10:28:05 +1000, Peter Stefanos
<peterATpennywiseDOTcomDOTau> wrote:

>Nick,
>
>Your suggestion for the queue is fine for not holding up the thread. I 
>had already considered this but then you would need something like a 
>timer checking the queue for events. I need to know about events quickly 
>and having a timer checking every millisecond or so doesn't seem to be 
>the most elegant way of doing it.
>
No need for a TTimer. You could use an event property, like "OnEvent".
Since the most important thing here is not to mess up the worker
thread with the User Interface, the "OnEvent" handler could only set
up a boolean variable, like "EventAvailable" and return immediately.

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 B. Cassos