Ok, I've tracked through the VCL code to see what happens and the issue
is with TForm. Mousewheel messages get special handling and are passed
to TCustomForm.MouseWheelHandler which directs the message to the active
control.
So I can just override that method in the main app form and direct it to
our control if the mouse is over it.
Phil.
Phil Middlemiss wrote:
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.
_______________________________________________
Delphi mailing list
[email protected]
http://ns3.123.co.nz/mailman/listinfo/delphi
begin:vcard
fn:Phil Middlemiss
n:Middlemiss;Phil
org:Vision Software, MTS Ltd
email;internet:[EMAIL PROTECTED]
title:Project Leader
tel;work:+64 7 3480001
tel;cell:+64 27 4592648
x-mozilla-html:TRUE
url:http://www.tumonz.co.nz
version:2.1
end:vcard
_______________________________________________
Delphi mailing list
[email protected]
http://ns3.123.co.nz/mailman/listinfo/delphi
