If you want a function in your DLL to send a message to the main UI
window
you could just have a CWnd* member in the DLL object that is set to NULL
by
default, but is settable by the application consuming the DLL. Then when
the window object is non-null you could PostMessages to it that the main
application window handles. Consumers of the DLL will have to set up the
message handler and identify the window to which to post messages, but
this
is pretty academic.
If you are going the other way, you want to send a message to the DLL's
window you could have a GetMsgWindow() function (or something like that)
that returns the CWnd * where you want the application to post messages
the
DLL's window intends to receive. However, you could self contain this in
the DLL by simply having callable functions that post their own messages
as
needed which would be a lot easier.
Tom
"Stephen Myers" <StephenMyers@discussions.microsoft.com> wrote in message
news:9FD646D5-7E1C-498E-AACE-2E1B28788EE6@microsoft.com...
I???m creating a UI thread from a Regular DLL. I would like to use the
equivalent of PostMessage(???) to send data back to the CWinApp (for the
DLL)
for processing.
I???m considering creating an invisible window and allowing it to handle
things. Is there a better solution?
Thanks in advance.
(Environment is VS 2003)
Most of what's going on is internal to the DLL. It just seems sort of