Re: afxMapHWND with Shared Release DLL
"DSXC" <dsxc80@gmail.com> wrote in message
news:1371b54ciduefc9@corp.supernews.com...
Well the reason behind calling the afxMapHWND is because I'm passing a
HWND which is not in the map down as a parent window. Without passing
this the parent window asserts on creation (CWnd::AssertValid function) at
the point where it is checking if the CHandleMap is valid. If there is a
way to pass a parent CWnd from an EXE into a child CWnd inside a DLL I'd
like to know - all of the DLL's are loaded via LoadLibrary. The parent
CWnd is to a tab control within our container application, the DLL's pass
CDialog back to the parent via a create method. The CDialog is then shown
on the tab control using ShowWindow(SW_SHOW) when it is the selected tab
(and SW_HIDE when it is not). It works fine when the CDialogs are created
within the container application, but not within the DLL.
At the moment I'm sticking with MFC from an ease of use point of view
(haven't used ATL for probably 3 years, so it means remembering stuff I
haven't used for a while), but if there is no way of doing this I may have
to go back to ATL.
I would try to resolve this in MFC, as it is the easier route than dumping
it and going to ATL.
As Asm hints, if you pass CWnd * between your .exe and .dll, you need to
make sure both are NOT statically linking MFC. This is because both .exe
and .dll need to be using same copy of MFC so that both have the CWnd in the
map. (If you statically link MFC, there is a separate copy running in .exe
and another in .dll, and these don't know about CWnd's in the other.)
If you did want to statically link MFC (like I love to do), then what you
would do is pass HWND between .exe/.dll and when the receiver gets it, it
can do a CWnd::Attach() on it to associate the HWND to a CWnd in that
module's MFC HWND map.
-- David