Detecting mouse click on a window known only by handle

Question

0.00/5 (No votes)

See more:

.NET3.5

Hi
I have created a class to use several webcams to fit my own needs using the avicap32.dll. Webcam features such as eyetracking and recording function properly. I'm however facing a small setback that mouseclicks are no longer detected when clicking the user control. I blame this on the following line of code. pn is a panel in the usercontrol.

<br />
hWnd = Webcam.capCreateCaptureWindowA("0", Webcam.WS_VISIBLE | Webcam.WS_CHILD, 0, 0, 0, 0, pn.Handle, 0);<br />

This line sort of overlaps the panels I use to draw the webcam images on, so I can't actually click them.
Is there a way to detect these event by using WindowProc of the parent form or hooking into the created window? Or is there a cleaner way to solve this? I already looked into SetWindowLongPtr, but this seems kind of dirty business to me because of subclassing and I wouldn't want to mess with those things since I am running out of time...
I specifically want to let the user define a set of points on the webcam image. Just the coordinates.

Thanks in advance

Posted 12-Dec-10 4:01am

Steven Solberg

Updated 12-Dec-10 4:03am

v2

Add a Solution

2 solutions

Solution 2

Found my own answer involving hooking the created window.
This is the link I found. May it serve future readers as it served me ;)

http://www.eggheadcafe.com/software/aspnet/33974118/-subclassing-an-unmanaged-wndproc.aspx[^]

Posted 12-Dec-10 7:38am

Steven Solberg

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

pasztorpisti · Accepted Answer · 2010-12-12T07:29:00

I would go on with hooking. There is an article here that may help you to intercept mouse messages in the parent window (I haven't tried it), but even if its working I think that the hooking is the cleaner (and 100% working) solution, and maybe the only one. Unfortunately there are a lot of scenarios in GUI programming when the only solution is hooking. It isn't that dirty solution as it seems to be for the first time, just hide the above window creation call and the hooking to a class and don't think of it again! :laugh: