Re: MFC and User Defined objects

Greetings,

Scott you said,

A CWnd object such as CDummyDlg does not have a window (so it does
not
have a valid m_hWnd) when it is constructed. It only has a window
and
valid m_hWnd after its Create (or DoModal) function is called. The
design of MFC requires this "two stage construction".

How can I make my code wait/suspend until Create or DoModal has run?
That is how can I provide mechanism in my code to suspend thread
creation or further code execution until a valid HWND is available?
How can I check if it has run?

Furthermore:

You created 'mywin 'as a local variable. That means it does not
exist
outside the function where it was created. See C++ "scope" rules.

Initially, I had declared 'mywin' to be of HWND datatype inside
CDummyDlg class declaration as Private data member. To my
understanding all member functions should have access to Private data
members in same class. I would get an error message about something
being static inside adapter code(sorry can't remember exact message).
Everything is part of CDummyDlg, including thread creation functions.
Since thread functions are also part of same class as 'mywin' they
should be able to access it. I tried making 'mywin' Public still I
was getting an error. Finally, I took it and placed it inside the
CDummyDlg::Run() function (which actually creates threads).
Therefore, 'mywin' was local to that function and I was passing it to
thread code. But it would fail. As I understand, it doesnt matter if
I pass a datatype which is local because point is as long as I have
valid data to pass-it should work in thread code. Thats where I was
getting undeclared variable message in adapter code. Then I made
'mywin' global and everything worked like a charm. So it was trial
and error but I want to understand good engineering principles.