> In order for incoming communications to succeed, certain Windows
> messages need to be allowed to pass through the message pump. If you
> don't allow those messages, no inbound comms. But does anyone know
> what those messages are these days? It used to be WM_COMMS or
> WM_COMMSNOTIFY (I think), but they no longer exist. I tried using
> Spy++ on a VB program, but that didn't help identify the message.
Well, I don't know how well it's possible to intercept the message pump
in the VB program, but here are my suggestions (don't know even if
they're implementable in VB):
Replace the whole message loop with your own, and start logging all the
messages in a log file. For each message, log the code, HWND (even if
it is NULL, which means a thread message), WPARAM, and LPARAM. Also,
log the return value of InSendMessageEx( ).
Now, if you have more knowledge than I do on how the comm messaging
system is implemented, you can interpret the results more easily. For
example, COM creates its own window, and you can check its HWND to
figure out what messages are related to COM stuff, and what messages are
related to your own window. Maybe the comm system uses a technique like
this, or maybe it posts thread messages (HWND == NULL). You should try
to point out some messages which are different to others in some
considerable way. I personally guess you can get good information by
the HWND parameter, since I believe that the comm system should be
creating its own window instead of yours to handle its job (to make sure
it runs in non-GUI environments as well, for example) - but it's only a
guess.
-------------
Ehsan Akhgari
List Owner: [EMAIL PROTECTED]
[ Email: [EMAIL PROTECTED]; [EMAIL PROTECTED] ]
[ WWW: http://www.beginthread.com/Ehsan ]
"The brightest future will always be based on a forgotten past."
