DataGridView using CellContentClick event

Question

1.00/5 (1 vote)

See more:

I created DataviewGrid manually. When fires CellContentClick event, it fires the event more than once. Does anyone have any idea what may trigger the problem and how to fix it?

Posted 20-Jan-16 9:22am

Kay Alexander

Add a Solution

Comments

Kevin Marois 20-Jan-16 15:28pm

Check to see how many times you're subscribed to the CellContentClick event.

1 solution

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)

Sergey Alexandrovich Kryukov · Answer 1 · 2016-01-20T12:21:00

You did not provide any code to help you to fix the bug, so I can only tell you what to do in such situations in general.

Probably you already can see that your event handler is called twice, even when the user makes only one click. This is good; probably it means that you used the debugger. There can be two general source for such doubling: your event handler is added twice (or more times) and the event is invoked twice. In all cases, here is what you can do:
Set a break point on the first statement of your event handler. Run the application and click on the cell. The execution will stop on your break point. Continue stopped execution; do it again and again until UI appears again without any more stopping at the break point. For all such stops, look at the debug window "Call stack". It will show you where the call comes from. Visiting different places on the call stack on each stop, you will be able to see the source of the problem.

—SA