C / C++ / MFC

Mark Salsbery wrote:

1) You're creating a worker thread when you need a UI thread.

Mark Salsbery wrote:

2) How are you going to close the WaitDlg if it's in a modal loop?

Mark Salsbery wrote:

The code that locks up - where is that, on what thread is it executing, and
what is hWndParent?

Mark Salsbery wrote:

Are you giving the second-thread dialog a parent? That can cause problems in MFC
if the parent and child were created on different threads.

Mark Salsbery wrote:

Regardless, what you're doing is so much simpler using a modeless dialog on the UI thread.

Bram van Kampen wrote:

does the existence of a Parent CWnd Class suffice, or do we need to create the underlying window (albeit Invisible)

Bram van Kampen wrote:

Any chance of a brief outline of how to do that?

Mark Salsbery
Microsoft MVP - Visual C++

Mark Salsbery wrote:

From the main UI thread, create the CDialog object. Use Create()
instead of DoModal() to create the window (HWND).
Communication with the window can be done using window messages,
which can be posted from any thread.

// Program logic.
void sum(int a, int b)
{
    int c = a + b;
    return c;
}

// Driver
void main()
{
    int a, b;
    printf("Enter first number: %d", &a);
    printf("Enter second number: %d", &b);

    int c = sum(a, b);
    printf("Sum of two numbers is: %d\n", c);
}

livin lie wrote:

I also have no clue how to write a driver...

OverdoS wrote:

I don't even know if I wrote the code properly. Any help is appreciated

Renjith Ramachandran wrote:

Do you know any products which helps to do all of these?

sashoalm wrote:

Can Visual Studio detect dead code btw?