views:

565

answers:

2

Hi,

I've got a text box bound to an object's property (in fact several text boxes) on a form. This for is an editor for an object. When i'm editing some objects and modify values in the one of the text boxes i can't exit from the text box (neither by tab nor clicking on another text box). However that's not always the case - when editing other objects (of the same type) it works fine.

Here's a code snipet:

txtValue.DataBindings.Add("Text", _SourceObject, "PlannedValue", True, DataSourceUpdateMode.OnPropertyChanged, Nothing, "c")
txtEstPlacements.DataBindings.Add("Text", _SourceObject, "EstimatedPlacementCount")
txtReference.DataBindings.Add("Text", _SourceObject, "Reference")

Any suggestions?

+2  A: 

Sounds like a data validation issue. Check if the controls on the form have their CausesValidation properties set to true or false.

Also check the AutoValidate property on the form. It is probably set to EnablePreventFocusChange (which is the default).

It may also be the case that the value being supplied in the text box can not be converted to the type of the property it is bound to on the source data object. I believe the Convert class is used for this (though I may be wrong here).

You may want to check out this article on MSDN that covers winforms validation in some detail.

orj
Thanks! Setting form's AutoValidate property to EnableAllowFocusChange worked.
Muxa
+1  A: 

If your Form has AutoValidate==EnablePreventFocusChange, then you'll end up with the focus stuck in any field that fails validation.

Note that validation is considered to have failed if there is an exception when writing the value into the object.

Try setting a breakpoint at the entry point of the setter of the property that's bound to the control where the cursor gets stuck. Then, single step to see if an exception is raised.

If the breakpoint never fires, the exception may be occuring within the Databinding framework.

Contrary to popular believe, the databinding framework does log errors and other useful information - it uses support from the System.Diagnostics namespace to do this. I forget the details, but they're on MSDN - you should be able to view the diagnostics in the messages window of Visual Studio while your application runs. Very useful for troubleshooting issues with Databinding.

Bevan