How To Implement IMessageFilter

[GrandpaB]

Hi,

I recently had a post about how to block Mousewheel events. The answer was
to implement an IMessageFilter. Sadly, I must report that after 24 hours of
researching my library and online resources I am still stumped! I did find a
promising code snippet on MSDN, but have yet to successfully implement it.

Here is the code snippet:

Public Class MessageFilter

Public Class TestMessageFilt er
Implements IMessageFilter

Public Function PreFilterMessag e(ByRef m As _
System.Windows. Forms.Message) _
As Boolean Implements IMessageFilter. PreFilterMessag e
'Blocks all the messages relating to the left mouse button.
If ((m.Msg >= 513) And (m.Msg <= 515)) Then
Console.WriteLi ne("Process messages: " & m.Msg)
Return True
End If
Return False
End Function
End Class

End Class

I have three basic questions about this code. 1.) How do I specify the
parameter ‘m’ when I call the PreFilterMessag e function? 2.) Where in my
code do I insert the PreFilterMessag e function? 3.) Where to the constants
513 and 515 in the ‘If’ statement come from and how must I change this to
block messages relating to the Mousewheel?

Thanks for your assistance and patience.
--
GrandpaB

[m.posseth]

With a messagefilter you can catch / cancel all events sent to the window
and its controls ( equivalant of subclassing a form in VB6 )

the problem is you need to find the right event code for the message you
want to cancel

here is an example http://www.freevbcode.com/ShowCode.Asp?ID=5635 where it
is jused to dissable the webrowser control`s accelerat
or keys
regards

Michel Posseth [MCP]
"GrandpaB" <Gr******@discu ssons.microsoft .com> wrote in message
news:7E******** *************** ***********@mic rosoft.com...

Hi,

I recently had a post about how to block Mousewheel events. The answer
was
to implement an IMessageFilter. Sadly, I must report that after 24 hours
of
researching my library and online resources I am still stumped! I did
find a
promising code snippet on MSDN, but have yet to successfully implement it.

Here is the code snippet:

Public Class MessageFilter

Public Class TestMessageFilt er
Implements IMessageFilter

Public Function PreFilterMessag e(ByRef m As _
System.Windows. Forms.Message) _
As Boolean Implements IMessageFilter. PreFilterMessag e
'Blocks all the messages relating to the left mouse button.
If ((m.Msg >= 513) And (m.Msg <= 515)) Then
Console.WriteLi ne("Process messages: " & m.Msg)
Return True
End If
Return False
End Function
End Class

End Class

I have three basic questions about this code. 1.) How do I specify the
parameter 'm' when I call the PreFilterMessag e function? 2.) Where in my
code do I insert the PreFilterMessag e function? 3.) Where to the
constants
513 and 515 in the 'If' statement come from and how must I change this to
block messages relating to the Mousewheel?

Thanks for your assistance and patience.
--
GrandpaB

[Claes Bergefall]

1. You don't call PreFilterMessag e, the framework does. You will need to
tell the framework that you have implemented it though. You do this by
calling Application.Add MessageFilter

2. You can implement IMessageFilter in any class you want. I usually do it
in the MainForm and then call AddMessageFilte r(Me) from the Load event
handler.

3. The constants can be found in one of the header files (.h) found in the
folder C:\Program Files\Microsoft Visual Studio .NET
2003\Vc7\Platfo rmSDK\Include. You will need to install the C++ part of
Visual Studio to have that directory though. If you can't do that you can
instead install the PlatformSDK which you can download from
<http://www.microsoft.com/downloads/d...128F-A770-45F1
-86F3-7AB010B398A3&di splaylang=en>. The constant you're interested in can be
found in winuser.h and is defined like this:

Private Const WM_MOUSEWHEEL As Integer = &H20A
"GrandpaB" <Gr******@discu ssons.microsoft .com> wrote in message
news:7E******** *************** ***********@mic rosoft.com...

Hi,

I recently had a post about how to block Mousewheel events. The answer was to implement an IMessageFilter. Sadly, I must report that after 24 hours of researching my library and online resources I am still stumped! I did find a promising code snippet on MSDN, but have yet to successfully implement it.

Here is the code snippet:

Public Class MessageFilter

Public Class TestMessageFilt er
Implements IMessageFilter

Public Function PreFilterMessag e(ByRef m As _
System.Windows. Forms.Message) _
As Boolean Implements IMessageFilter. PreFilterMessag e
'Blocks all the messages relating to the left mouse button.
If ((m.Msg >= 513) And (m.Msg <= 515)) Then
Console.WriteLi ne("Process messages: " & m.Msg)
Return True
End If
Return False
End Function
End Class

End Class

I have three basic questions about this code. 1.) How do I specify the
parameter 'm' when I call the PreFilterMessag e function? 2.) Where in my
code do I insert the PreFilterMessag e function? 3.) Where to the constants 513 and 515 in the 'If' statement come from and how must I change this to
block messages relating to the Mousewheel?

Thanks for your assistance and patience.
--
GrandpaB

[Herfried K. Wagner [MVP]]

"GrandpaB" <Gr******@discu ssons.microsoft .com> schrieb:

I recently had a post about how to block Mousewheel events. The answer
was
to implement an IMessageFilter. Sadly, I must report that after 24 hours
of
researching my library and online resources I am still stumped! I did
find a

<URL:http://dotnet.mvps.org/dotnet/samples/operatingsystem/ScreensaverStar t.zip>

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://classicvb.org/petition/>

[GrandpaB]

This is a group thanks for your responses. The IMessageFilter is now working
in my application. The application creates, edits and deletes records in a
database. The user was complaining that occasionally data in some records was
changing. The only data fields with which they had difficulty had comboBoxes
as their sources. The users swore that they never touched the mousewheel so
it was my problem. I, of course, blamed Bill Gates.

The Enter and Leave events for the comboBoxes now have an AddMessageFilte r
and RemoveMessageFi lter statements. If this doesn't resolve the problem I'll
know that it really is Bill Gates' fault.

Thanks again,
--
GrandpaB