🚀 go-pugleaf

Remy Lebeau (TeamB) wrote:
>"Steve Aletto" <steve_alettoANTI@SPAMhotmail.com> wrote in message
>
>
>You are assuming that Sara wants the code to loop.  That may not be the
>actual case.  Looping is not a requirement for threads.

It did sound like she was re-executing the same thread from main.
Past message threads have made it sound like thread destruction isn't
instantanious, that they "hang around" indefinately until MS gets
around to cleaning up. Having a (repetitivly used) thread stay alive
for the duration of the application seems like a simple enough work
around.

Agree Steve's answer may have been a bit short on deatils though.
Perhaps the thread could suspend itself, so main could wake it up to
cycle through again. Or, setting a terminate flag first, wake it up to
self-terminate at program's end. (Again, I don't know details of VCL
or TThread, so just blue-skying)

>> void __fastcall CMyThread::Execute(void)
>> {
>>     while (!Terminated)
>>     {
>>         // Process here

	if( !ThreadTerminate )
		Suspend();
	if( ThreadTerminate )
		break;
>>     }
>> }

main()
{	ThreadTerminate=false;
	thread = new TThread(function,suspended);
	while(app running)
	{
	}
	ThreadTerminate=true;
	thread.Resume();
	WaitForSingleObject( threadID
	delete thread;
}
OnStartThreadButtonClick()
{	thread.Resume()
probably need an interlock so you don't resume a running thread.
}