// Name: validator.h
// Purpose: topic overview
// Author: wxWidgets team
-// RCS-ID: $Id$
-// Licence: wxWindows license
+// Licence: wxWindows licence
/////////////////////////////////////////////////////////////////////////////
/**
@page overview_validator wxValidator Overview
-Classes: wxValidator, wxTextValidator, wxGenericValidator
-
-@li @ref overview_validator_intro
-@li @ref overview_validator_anatomy
-@li @ref overview_validator_dialogs
-
-
-<hr>
-
-
-@section overview_validator_intro Example
+@tableofcontents
The aim of the validator concept is to make dialogs very much easier to write.
A validator is an object that can be plugged into a control (such as a
Note that any wxWindow may have a validator; using the @c wxWS_EX_VALIDATE_RECURSIVELY
style (see wxWindow extended styles) you can also implement recursive validation.
+@see wxValidator, wxTextValidator, wxGenericValidator, wxIntegerValidator,
+ wxFloatingPointValidator
+
+
@section overview_validator_anatomy Anatomy of a Validator
You can optionally define event handlers for the validator, to implement
filtering. These handlers will capture events before the control itself does
-(see @ref overview_eventhandling_processing).
+(see @ref overview_events_processing).
For an example implementation, see the @c valtext.h and @c valtext.cpp files in the
wxWidgets library.
-wxwindow::SetExtraStyle( wxWS_EX_VALIDATE_RECURSIVELY )
-
@section overview_validator_dialogs How Validators Interact with Dialogs
dialog resource.
*/
-