Controls such as the TextBox fire Validating and Validated events as part of the validation mechanism that is provided by WinForms. This allows you to prevent the focus leaving a control if there is an error in that data entry field. Unfortunately the majority of the Krypton Toolkit controls do not fire these events directly.
Most Toolkit controls such as the KryptonTextBox are actually made up of two parts. The KryptonTextBox itself is a container that has a single child control which is just a standard TextBox. This is done so that the container can draw the border around the inner control and then the inner control can be instructed to draw without a border. An approach required so that the correct border is drawn according to the Krypton Palette definition. It does however have the complication that many of the events of interest are fired by the inner control. To get around this the container hooks the events of the inner control and then fires them again from itself. So as a developer you just hook the container and it fires the events you expect, without most developers realising that the event actually originated from the inner control.
Turns out that I missed a couple of events. So I have now updated the source code so that the Validating and Validated events from inner controls are now fired from the container. This makes it much easier to get the validation mechanism to work. The controls affected by this are…