[DUG] Capturing mouse wheel

[Rohit Gupta]

My interpretation of what I saw was different.  I observed that the parent of 
the component was getting the messages.  So I simply got the parent panel 
to pass them on as events to the component.  This may or may not work for 
you.

Date sent:	Thu, 27 Jul 2006 09:17:51 +1200
From:	Phil Middlemiss <phil at tumonz.co.nz>
Organization:	MTS Ltd
To:	NZ Borland Developers Group - Delphi List <delphi at ns3.123.co.nz>
Subject:	[DUG] Capturing mouse wheel
Send reply to:	NZ Borland Developers Group - Delphi List <delphi at ns3.123.co.nz>
	<mailto:delphi-request at ns3.123.co.nz?subject=unsubscribe>
	<mailto:delphi-request at ns3.123.co.nz?subject=subscribe>

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?

Phil.
Regards

Rohit

======================================================================
CFL - Computer Fanatics Ltd.  21 Barry's Point Road, AKL, New Zealand
PH    (649) 489-2280 
FX    (649) 489-2290
email rohit at cfl.co.nz  or  r.gupta at xtra.co.nz
======================================================================