🚀 go-pugleaf

"Jeff Douglass" <.> wrote in message
news:3ea8274c$1@newsgroups.borland.com...

> The message is simply defined as
> #define THE_MESSAGE (WM_USER + 3332)

I would suggest you consider having a look at the RegisterWindowMessage()
function.  The one gotcha with hard-coded message IDs is that you never know
when someone else is using the same ID for their own stuff.  Especially in a
scenerio where you're broadcasting the message to everyone.  Using
RegisterWindowMessage() ensures you have a unique value that only you know
how to interpret (and anyone else specifically written to directly support
your message).

> The only thing I can think is the problem is that the startup
> window is not a "top level window"

Very possibly.  VCL forms are not stand-alone.  They are actually children
of the hidden global TApplication window, which is the true top-level window
for the program.  You will probably need to assign an event handler to the
TApplication::OnMessage event in order to intercept your broadcast
correctly.  Otherwise, you'll have to override the form's CreateParams()
method to reassign the owner window (in API terms, not VCL) to be the main
Desktop window instead.  That might have other side-effects on how the VCL
form behaves, though.


Gambit