\item propform.h: wxPropertyListView and associated classes
\end{itemize}
-
-
-
-
-
-
-
-
\section{Topic overviews}\label{proplistoverviews}
This chapter contains a selection of topic overviews.
may like to work out how the form view could be extended to provide some of the
functionality of the property list!
-Validator objects may be associated explictly with a wxProperty, or they may be
+Validator objects may be associated explicitly with a wxProperty, or they may be
indirectly associated by virtue of a property `kind' that matches validators having
that kind. In the latter case, such validators are stored in a validator registry
which is passed to the view before the dialog is shown. If the validator takes
`edit a button', or rather, edit the button's properties. One of the
properties you can edit is {\it width} - but there is no explicit
representation of width in a wxWindows button; instead, you call SetSize
-and GetSize members. To translate this into a consisent,
+and GetSize members. To translate this into a consistent,
property-oriented scheme, we could derive a new class
wxButtonWithProperties, which has two new functions: SetProperty and
GetProperty. SetProperty accepts a property name and a value, and calls
wxButtonWithProperties::SetProperty to transfer the wxProperty value back into the button
by way of an appropriate call, wxWindow::SetSize in the case of width and height properties.
-
-
\section{Classes by category}\label{proplistclassesbycat}
A classification of property sheet classes by category.
\item \helpref{wxPropertySheet}{wxpropertysheet}
\end{itemize}
-
\subsection{Validator classes}\label{proplistvalidatorclasses}
Validators check that the values the user has entered for a property are