Launching a threaded Dialog but it doesn't allow me access to the parent window

[bman1176]

using: Microsoft VC++ and MFC

I am trying to thread off a Dialog when I click on a button, that way I launch several dialogs from a particular Dialog.

example:


void CTestthreadDlg::OnButton1()
{
//does not allow acess to this dialog that is calling
AfxBeginThread(ThreadFunction, tm);
}

void CTestthreadDlg::OnButton2()
{
//this dialog will allow me access to this dialog that is calling after I click my messagboxes.
AfxMessageBox("START");
AfxBeginThread(ThreadFunction, tm);
AfxMessageBox("AFTER");
}

///////////////////////////////////////////////////////////////////////

UINT ThreadFunction(LPVOID pParm)
{
//AfxMessageBox("HELLO");
threadManager tm;
tm.DoModal();
return 0;
}

[master5001]

I'm not too familiar with MFC but I am a little familiar with multithread apps. By default a child thread can't access the parent. You can change the SECURITY_ATTRIBUTES so that the child has access but this is assuming you are working with the NT kernel since win32 doesn't care too much about security. Also why do you need the child to have access to the parent? The child should be doing something independant of the parent thread.

[Sebastiani]

Geez I hate MFC...anyway, passing info between threads isn't trivial, rather, it can be a little complicated. The simplest way to do it is to make the data global. I am not kidding! Next, you could look int CreateNamedPipe(), CreateFileMapping() and similar, which I will leave up to you to research. Finally, you can pass a pointer to the data as a message to the interested thread! However, YOU MUST SEND IT USING THE WM_COPYDATA message. Unfortunately, I do not remember how exactly to implement that, but suffice it to say: threads are not intended for "weekend programming", and if you REALLY want to use them, you do a little/lotta research