3

I have written an application that currently handles clicks from multiple mouse devices.

I used this project and modified to handle mouse clicks as apposed to keyboards.

This is working fine, however now I need to know if there is a way to suppress a click event if it has been handled by my app. The app is a quiz game so the idea is that the quiz master will have (and still be able to use) 1 mouse, and the other contestants will have their own mouse (as buzzers). So when they buzz in, I don't want the mouse click events to fire in the operating system (or at least this application).

The concept is the familiar override of void WndProc(ref Message message), and so I have tried not calling base.WndProc(ref Message) when I don't want the click events to fire, but this has not worked.

Can anybody point me in the right direction here?

Should I be going down the windows hook route? I have looked at this, but I can't seem to work out how I could hook to each mouse device individually.

Any help would be greatly appreciated.

Edit:

This is a Windows Form UI project, and not WPF. So the MultiPoint SDK from Microsoft won't work.

Bridge
  • 29,818
  • 9
  • 60
  • 82
user1830285
  • 578
  • 8
  • 24
  • 1
    Is there anything in the Microsoft Multipoint SDK? http://www.microsoft.com/multipoint/mouse-sdk/showcase.aspx - it has support for handling input from multiple mice. – dash Jan 25 '13 at 09:22
  • You beat me to it, i was going to say, i should mention that im using Windows Forms UI, and not WPF. I had already looked at the multipoint SDK. – user1830285 Jan 25 '13 at 09:24
  • A windows hook won't work, this requires raw input through WM_INPUT. Pinvoke required. – Hans Passant Jan 25 '13 at 13:13
  • So there is no way to achieve this? – user1830285 Jan 28 '13 at 15:42

1 Answers1

2

The solution to this lies within not WndProc, but PreFilterMessage(). By intercepting messages before they even reach the form, you can remove them from the message pump causing them to never reach the control that was clicked. This also works for child controls within the form.

I answered this and posted the full source in the following question:

C# Get Mouse handle (GetRawInputDeviceInfo)

Community
  • 1
  • 1
user1830285
  • 578
  • 8
  • 24