Is "Create window in Work thread" a bad design?

[fitatc]

My friend "Create window in Work thread" when she need a message pump (message loop? I am not sure, sorry I am a beginner). She just create a window, and then do a loop like WndProc does. :confused:I am also worry about if it could work I know that MFC has a UI thread that with a message Pump can do this without creating a window. But I cannot persuade she to use UI thread instead of a "Work thread with window", because of my pity knowledge :( . could any one help me about that.

[_Superman_]

The only difference between a UI thread and a worker thread is that a UI thread has a message loop. So what your friend has created is a UI thread rather than a worker thread.

«_Superman_»

[Joshua Tully]

There's an article on this site that discusses worker and UI threads and here you go http://www.codeproject.com/KB/threads/usinguithreads.aspx[^]

[fitatc]

Thanks for answer my qustion, «_Superman_» and Josh_Jackson :laugh: I trace to the source code of the CWinThread into thrdcore.cpp. (1) CWinThread is derived from CCmdTarget, That bring to CWinThread the Message_Map so it can get message from OS???:confused: (2) If so Why CWinThread need a CWnd in UINT APIENTRY _AfxThreadEntry(void* pParam)

UINT APIENTRY _AfxThreadEntry(void* pParam)
{
.....
CWnd threadWnd;
TRY
{
.... if (pApp != NULL &&
pThread->m_pMainWnd == NULL && pApp->m_pMainWnd->GetSafeHwnd() != NULL)
{
// just attach the HWND
threadWnd.Attach(pApp->m_pMainWnd->m_hWnd);
pThread->m_pMainWnd = &threadWnd;
}