Re: Heavy Tooltip-Problems in mixture of MFC Regular and Extension DLL

From:

Scot T Brennecke <ScotB@Spamhater.MVPs.org>

Newsgroups:

microsoft.public.vc.mfc

Date:

Sat, 06 Jun 2009 16:33:52 -0500

Message-ID:

<4A2AE0C0.1050805@Spamhater.MVPs.org>

I'm not sure why you want to avoid MSDN. However, the MFC source code
itself is completely at you fingertips for truly understanding the
internals. Search the source code for these structs, variables, and
APIs to get a much better understanding:
- AFX_MODULE_STATE
- AfxGetModuleState
- AfxGetStaticModuleState
- AfxGetAppmoduleState
- AFX_MODULE_THREAD_STATE
- _AFX_THREAD_STATE
- AfxGetThreadState
- AFX_MANAGE_STATE
- _AFX_BASE_MODULE_STATE
- _AFX_DLL_MODULE_STATE
- CDynLinkLibrary
- AfxGetApp
- AfxFindResourceHandle
- AfxGetResourceHandle
- CCmdTarget::m_pModuleState

Also, when reading the above code, it is imperative to understand that
_AFXDLL is defined when you are using the MFC shared DLLs, and when MFC
itself is built for the shared DLL, rather than the static library.

MueMeister wrote:

Hi Ajay,

thanks for your support. I have to admit that I have been developing
simple MFC applications but never got in touch deeper with the MFC.
Thanks for your help.

If you have some good links where such details (module state, thread
state of different MFC components in a process -> but not MSDN) are
explained I would be delighted to get them.

MueMeister

Ajay wrote:

On Jun 3, 2:18 pm, MueMeister <m...@gmx.de> wrote:

The DLLs 'B' and 'C' expose classes which are derived from types
exposed by the extension DLL 'A' (Especially dialogs are created).
So, I thought if e.g. CString is used in the regular DLLs 'B' and 'C'
I need MFC in those DLLs, too ?! Maybe I have a misunderstanding here!

I think problem is based on where is the dialog created. If the dialog
is created in App(static link), its going to use that module's MFC
state. However if the code/callback is in DLL, that is going to use
state of that specific module. There is no way for you to control it
because its MFC's internal code(unless you rewrite the code).

Its just a mess; something you shouldnt do(multiple version of MFC in
same process). Even if you are able to escape it now for this issue,
its going to bite the next day on something else.

--
Ajay