wxFont can now raelly use the native fonts

[wxWidgets.git] / docs / latex / wx / proplist.tex

diff --git a/docs/latex/wx/proplist.tex b/docs/latex/wx/proplist.tex
index fb4036e9c5de68b30939da72a5b803c75fc57297..f9ce7a77a2ac58a8fcc763b409dcf65494f22bf9 100644 (file)
--- a/docs/latex/wx/proplist.tex
+++ b/docs/latex/wx/proplist.tex
@@ -99,14 +99,6 @@ The property class library comprises the following files:
 \item propform.h: wxPropertyListView and associated classes
 \end{itemize}
 
 \item propform.h: wxPropertyListView and associated classes
 \end{itemize}
 

-
-
-
-
-
-
-
-

 \section{Topic overviews}\label{proplistoverviews}
 
 This chapter contains a selection of topic overviews.
 \section{Topic overviews}\label{proplistoverviews}
 
 This chapter contains a selection of topic overviews.


@@ -341,7 +333,7 @@ one property, and there is no provision for invoking further dialogs. The reader
 may like to work out how the form view could be extended to provide some of the
 functionality of the property list!
 
 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
 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


@@ -461,7 +453,7 @@ example, in Visual Basic and similar programming environments, you can
 `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
 `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
 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


@@ -483,8 +475,6 @@ as described elsewhere, and the user edits away. When the user has finished edit
 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.
 
 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.
 \section{Classes by category}\label{proplistclassesbycat}
 
 A classification of property sheet classes by category.


@@ -497,7 +487,6 @@ A classification of property sheet classes by category.
 \item \helpref{wxPropertySheet}{wxpropertysheet}
 \end{itemize}
 
 \item \helpref{wxPropertySheet}{wxpropertysheet}
 \end{itemize}
 

-

 \subsection{Validator classes}\label{proplistvalidatorclasses}
 
 Validators check that the values the user has entered for a property are
 \subsection{Validator classes}\label{proplistvalidatorclasses}
 
 Validators check that the values the user has entered for a property are