G
Guest
Hello,
I am writing a Win32 multithreaded application in C which
initiates a DDE hot link connection in one of it's
threads. I have defined a DdeCallBack function globally. I
am using PeekMessage within the initiating thread to
determine when the WM_DDE_DATA message from the server is
generated due to a change in the topic items data. I have
successfully been able to Peek the WM_DDE_DATA message
from the server from within the thread, but it seems that
the DdeCallBack funtion associated with the conversation
is only called if I add a MessageBox call after the
PeekMessage call? Does anyone know if the DdeCallBack
function must be defined locally in the intitiating thread
to work properly? Or do I need to create some kind of
message loop in the thread to cause the DdeCallBack
function to be called? For some reason the app works fine
as long as I add a call to MessageBox, but I can not
determine why and I would like to be able to remove the
call to MessageBox. Thanks
I am writing a Win32 multithreaded application in C which
initiates a DDE hot link connection in one of it's
threads. I have defined a DdeCallBack function globally. I
am using PeekMessage within the initiating thread to
determine when the WM_DDE_DATA message from the server is
generated due to a change in the topic items data. I have
successfully been able to Peek the WM_DDE_DATA message
from the server from within the thread, but it seems that
the DdeCallBack funtion associated with the conversation
is only called if I add a MessageBox call after the
PeekMessage call? Does anyone know if the DdeCallBack
function must be defined locally in the intitiating thread
to work properly? Or do I need to create some kind of
message loop in the thread to cause the DdeCallBack
function to be called? For some reason the app works fine
as long as I add a call to MessageBox, but I can not
determine why and I would like to be able to remove the
call to MessageBox. Thanks