🚀 go-pugleaf

"Mattias Carleson" <mattias.carleson@commentor.se> wrote in message
news:3f27ad3f$1@newsgroups.borland.com...
> Now it works trapping WM_COMMAND from
> TButton and TBitBtn i WndProc. In
> Application->OnMessage it doesnt work

That is because the OnMessage event is only triggered for messages that are
posted into the message queue.  WM_COMMAND is not a posted message.  It is
sent directly to the window procedure of the destination window without
going through the message queue at all.

> But I still whant to trap the message when the user
> clicks a TSpeedButton

There is no such message for clicking a TSpeedButton because TSpeedButton is
not a true button to begin with.  It is a graphical control that simulates a
button.  It doesn't even have a window of its own.  That is what I was
trying to explain to you earlier.  You'll have to process the individual
mouse up/down messages instead.

> Ok, so I wrote the following code. It works, almost.
<snip>
> There is just one problem. When the form shows for the
> first time, clicking on the speedbutton or the toolbar/coolbar
> doesnt generate any WM_LBUTTONDOWN.

You are trying to intercept the message at the form level, but such messages
are not sent to the form unless you are clicking on the form itself.
Otherwise, they are sent to the TSpeedButton directly.  Not all messages go
through a parent window first.  For what you are trying to do, you will have
to subclass the TSpeedButton directly.

> A second question. I need to detect which
> speedbutton generating the message.

Since such messages to not provide any HWND specifying the target window,
then you will just have to translate the screen coordinates to client
coordinates and then enumerate the components looking for the component that
cooresponds to those coordinates.  Have a look at the
TWinControl::ControlAtPos() method.  You may have to call it recursively,
depending on your design.


Gambit