🚀 go-pugleaf

Carl Danley wrote:

>Alright, one more question I have... Every time a user clicks my 'Check for 
>Updates' button, it creates the thread that does the checking... Should I 
>recreate that threat everytime the button is clicked, like so:

I doubt they will be clicking regularly, so, yes
one click -> one thread seems reasonable.
But, I think if the user is capable of click-click-click-clicking
your button, it might cause some problems.
Ways to get around that:

Option 1: Use a mutex within the thread so if it is started
while the mutex is active (prior thread still running),
it will simply return.

Option 2: Set a global BOOL and check it in the OnClick.
OnClick()
{	if( ! Downloading )
	{	CloseHandle(CreateThread());
}	}
Thread()
{	Downloading = TRUE;
	{do the download}
	Downloading = FALSE;
}

Option 3: Disable the button.
Button1::OnClick()
{	Button1->Enabled = FALSE;
	CloseHandle(CreateThread());
}
Thread()
{	
	{download}
	Button1->Enabled = TRUE;
}

Problem is in remembering to close the handle, and
having the handle available for waiting in the OnClose()

Something else you could do...
Have the OnClose set the global terminating
flag and then exit (no waiting for the threads).
Have the thread check the flag each time it
tries to use the window handle (ignore GUI if terminating).

	if( ! Terminating )
		Button1->Enabled = TRUE;