| Name | Description |
|---|---|
| ElementValidationHandler | A manager for a single FrameworkElement. This is the lowest-level in Watchdog, where the controls are forced into error with an artifical dummy binding between two do-nothing DependencyProperty which are attached to the FrameworkElement and marked as invalid. |
| ElementValidationHandler.ArtificalValidationRule | A WPF ValidationRule which does nothing. Only exists so we have something to use with Validation.MarkInvalid(). |
| Field | Implementation of IField. It keeps track of handlers for each FrameworkElement that is attached to a field. |
| FrameworkElementExtensions | |
| SafeTypeToStringConverter | |
| SuspendableBindingConverter | A Decorator on another IValueConverter which will use the WatchdogBinding.SuspendTransfer flag to determine whether a transfer between source and target should actually occur or whether the a transfer should be stopped. |
| ValidationScope | The implementation of validation management for a portion of a WPF LogicalTree. When FrameworkElement register themseives with the scope, it figures which field they are associated with, typically through the the property name that the element is bound to. The scope also is given a ICollection{T}. When the collection is modified, the scope makes the association between the errors and the logical field that the error should be attached to. Additionally, the scope watches for any WPF Validation errors created by any controls under the scope. If found, they are inserted into the collection. This way the ViewModel layer of an application (which supplied the collection), is now aware of these types of error. |