[DUG] Capturing mouse wheel

[Conor Boyd]

I suspect the other component is calling the Win API method SetCapture,
which according to the API help:

"The SetCapture function sets the mouse capture to the specified window
belonging to the current thread. Once a window has captured the mouse,
all mouse input is directed to that window, regardless of whether the
cursor is within the borders of that window. Only one window at a time
can capture the mouse. "

Not sure what you do about it, but maybe that info is of some use.

HTH,

Conor

-----Original Message-----
From: delphi-bounces at ns3.123.co.nz [mailto:delphi-bounces at ns3.123.co.nz]
On Behalf Of Phil Middlemiss

We have a component that can use the mouse wheel - unfortunately, we
also use another component (not ours) that uses the mouse wheel. The
standard windows convention seems to be that whatever window has the
focus gets to process the message first. So even though the mouse is
over our component when the mouse wheel is rolled, the other component
gets the message.

I seem to remember some time ago seeing how to replace the main
TApplication message handler with your own, but can't remember how now. 
Is this possible? What is the technique?