What happens is that if validation fails (meaning, I set Cancel Event Args to true), the UI doesn't respond to input anymore. However, my textboxes are still working; the controls that locks up includes buttons, checkboxes, and nested tab Controls.Controls still respond to hover and click (meaning, the color changes), but no action is taken. For some context, my Validating handler begins by showing a Message Box (asking the user whether to save); if the result is "Cancel", I set e. I am dropped back to the same page, and the UI locks up as described.Here's the sequence of events: Bad data: (1) Validating.(I set ) (2) Parse (3) Binding Complete Good data: (1) Validating (2) Parse (3) Binding Complete (4) Validated ETA2: A bit more info and a work-around.
Specifically, I want to check that they have selected a radio button. Forms; namespace Tab Event Test I have encountered a similar bug, which happens even when I simply click on the tabs.
I don't check for this in the property setter, so I do the check in the validating event.
As you can see, from the above behaviour, the value, as a legitimate integer, will be written to the data source, even if I cancel validation.
In that case you should also somehow tell the user that there’s a problem with the field. For example, if the user presses Tab, clicks on another control, presses Enter to trigger the Accept button, or presses Esc to trigger the Cancel button.
For example, you could display an error message, change the field’s background color, or at least beep to let the user know that focus did not leave the field because something is wrong. The event triggers even if the user tries to close the form.