Re: Using MFC dll from non-MFC application
"JRGlide" <JRGlide@discussions.microsoft.com> wrote in message
news:79B758A2-7217-4451-B36C-122A26B04179@microsoft.com...
The original problem is that I couldn't get the MFC dll to remain
active.
It would become active for just a split second and then disappear.
What does this mean? DLL is loaded in memory unless you unload it, its
still there.
Here is the basic calling routine. (I'm actually trying to call it from a
MATLAB mex function which is a non_MFC dll. But this simplifies things
and
is what I use for testing.)
__declspec(dllimport) int ViewPointCloud (void);
int main(int argc, char* argv[])
{
ViewPointCloud();
return 0;
}
And this is the hook function in theApp:
__declspec(dllexport) void ViewPointCloud (void);
void ViewPointCloud (void)
{
AFX_MANAGE_STATE (AfxGetStaticModuleState());
}
So what happens is that the main function calls the hook function,
ViewPointCloud, which in turn invokes the dll as you said. But since the
hook function has nothing to wait on, it immediately returns to the main
calling routine which then exits, which I think causes the dll to unload
from
memory. I can't figure out how to get hook function to wait until the
user
is finished with the MFC program before returning, and unloading the dll.
I was going to suggest you do something like post a Windows message to the
calling app in CMainFrame::OnClose(), then in the calling program receive
the message and continue your processing,
ON_MESSAGE(UWM_VIEWPOINTCLOUDDONE,OnViewPointCloudDone)
but now you say the calling process is MatLab, which I don't think lets you
receive Windows messages.
Therefore, due to the limited nature of caller, I would encourage you to
leave the functionality in the .exe, and just launch the .exe from MatLab.
I'm pretty sure it has such a function that can wait until the .exe
terminates before continuing.
-- David