bindingsource property setter called twice why?

Question

2.00/5 (1 vote)

See more:

I a have a Checkbox on my form witch checked property is bound to a single object's boolean property. The update mode is set to OnPropertychanged cause there's no need for validation and i don't want the user having to click else where or press tab to commit that kind of change.

The problem is that the BindingSource calls the object's property setter a second time right after the checkbox looses focus just as if the update mode was OnValidation! That cause a terrible mess in my application...

The object implements the INotifyPropertyChanged but i removed the call to my helper method that raise the PropertyChanged event to see if that was the cause of that double call and it's not.

I just don't get it! why that behavior?

Posted 8-Nov-13 8:19am

Member 10349982

Add a Solution

Comments

Sergey Alexandrovich Kryukov 8-Nov-13 14:57pm

It is called twice because you programmed it this way, nothing else. How can we know what have you done? Use the debugger.
—SA

2 solutions

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 · 2013-11-08T09:00:00

Please see my comment to the question.

Such problems are easily resolved using the debugger with one of its wonderful tools: "Call Stack" window. If you use Visual Studio, use [main menu] Debug => Windows => Call Stack, and a breakpoint at the property setter. The stack will show you where the call comes at first place and other cases.

—SA

Member 10349982 · Answer 2 · 2013-11-08T09:33:00

I always make extensive use of all debugging features and logic to track problems like these, the call stack does not help unless i turn "just my code" off and dive into that stuff the debug output shows me. It sometimes help find errors in my own code but not always.

I solved this issue with that stupid kind of workaround i hate; by modifying my property setter in a way to ignore the unwanted call by comparing "value" with the Private Field of the class's property and it work like a expected.

I Just can't imagine working without Data Bindings but i frequently have to face situations like this with the bindingsource component.

bindingsource property setter called twice why?

2 solutions

Solution 1

Solution 2

Add your solution here

Preview 0