P
Pavel Dvorak
From my lengthy and painful debugging experiment it seems that
UserControl.ValidateChildren() will not envoke validation of child controls
where their CausesValidation property is false.
I have a rather complex hierarchy starting with a MS CAB SmartPart view
placed on an Infragistics UltraTabPageControl tab, which contains a group
box, a flow panel and finally some UltraComboEditors. When the
ValidateChildren method is run on the view (which inherits from
UserControl), it seems to validate only controls which themselves cause
validation. I implement Validating() event handlers accross the whole
hierarchy, set all CausesValidation to false except the bottom level of
combos where I play with various combinations to see the validation being
triggered.
This dependency seems so odd, because
1 - wasn't ValidateChildren ment exactly a mechanism independent on
(alternative to) auto validation controlled by CausesValidation property.
2 - CausesValidation is supposed to control behaviour of other controls, not
itself.
Am I right about my observation of this schizophrenic character of
CausesValidation, is it something particular to the Infragistics controls
library, or is something wrong in my test case?
Any comments appreciated.
Pavel
UserControl.ValidateChildren() will not envoke validation of child controls
where their CausesValidation property is false.
I have a rather complex hierarchy starting with a MS CAB SmartPart view
placed on an Infragistics UltraTabPageControl tab, which contains a group
box, a flow panel and finally some UltraComboEditors. When the
ValidateChildren method is run on the view (which inherits from
UserControl), it seems to validate only controls which themselves cause
validation. I implement Validating() event handlers accross the whole
hierarchy, set all CausesValidation to false except the bottom level of
combos where I play with various combinations to see the validation being
triggered.
This dependency seems so odd, because
1 - wasn't ValidateChildren ment exactly a mechanism independent on
(alternative to) auto validation controlled by CausesValidation property.
2 - CausesValidation is supposed to control behaviour of other controls, not
itself.
Am I right about my observation of this schizophrenic character of
CausesValidation, is it something particular to the Infragistics controls
library, or is something wrong in my test case?
Any comments appreciated.
Pavel