note about comctl32.dll bug with tree ctrl colours added

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

diff --git a/docs/latex/wx/custdobj.tex b/docs/latex/wx/custdobj.tex
index 2f2a71043ebc6d6f18fc22e4784f4f31b3018282..ffffc6ad7349ff313d67a9c1b4bf54e00a5f553e 100644 (file)
--- a/docs/latex/wx/custdobj.tex
+++ b/docs/latex/wx/custdobj.tex
@@ -1,6 +1,6 @@
 \section{\class{wxCustomDataObject}}\label{wxcustomdataobject}
 
 \section{\class{wxCustomDataObject}}\label{wxcustomdataobject}
 

-wxCustomDataObject is a specialization of
+wxCustomDataObject is a specialization of 

 \helpref{wxDataObjectSimple}{wxdataobjectsimple} for some
 application-specific data in arbitrary (either custom or one of the standard
 ones). The only restriction is that it is supposed that this data can be
 \helpref{wxDataObjectSimple}{wxdataobjectsimple} for some
 application-specific data in arbitrary (either custom or one of the standard
 ones). The only restriction is that it is supposed that this data can be


@@ -8,8 +8,8 @@ copied bitwise (i.e. with {\tt memcpy()}), so it would be a bad idea to make
 it contain a C++ object (though C struct is fine).
 
 By default, wxCustomDataObject stores the data inside in a buffer. To put the
 it contain a C++ object (though C struct is fine).
 
 By default, wxCustomDataObject stores the data inside in a buffer. To put the

-data into the buffer you may use either
-\helpref{SetData}{wxcustomdataobjectsetdata} or
+data into the buffer you may use either 
+\helpref{SetData}{wxcustomdataobjectsetdata} or 

 \helpref{TakeData}{wxcustomdataobjecttakedata} depending on whether you want
 the object to make a copy of data or not.
 
 \helpref{TakeData}{wxcustomdataobjecttakedata} depending on whether you want
 the object to make a copy of data or not.
 


@@ -20,9 +20,9 @@ the virtual functions mentioned below.
 \wxheading{Virtual functions to override}
 
 This class may be used as is, but if you don't want store the data inside the
 \wxheading{Virtual functions to override}
 
 This class may be used as is, but if you don't want store the data inside the

-object but provide it on demand instead, you should override
-\helpref{GetSize}{wxcustomdataobjectgetsize},
-\helpref{GetData}{wxcustomdataobjectgetdata} and
+object but provide it on demand instead, you should override 
+\helpref{GetSize}{wxcustomdataobjectgetsize}, 
+\helpref{GetData}{wxcustomdataobjectgetdata} and 

 \helpref{SetData}{wxcustomdataobjectsetdata} (or may be only the first two or
 only the last one if you only allow reading/writing the data)
 
 \helpref{SetData}{wxcustomdataobjectsetdata} (or may be only the first two or
 only the last one if you only allow reading/writing the data)
 


@@ -46,7 +46,7 @@ only the last one if you only allow reading/writing the data)
 \func{}{wxCustomDataObject}{\param{const wxDataFormat\& }{format = wxFormatInvalid}}
 
 The constructor accepts a {\it format} argument which specifies the (single)
 \func{}{wxCustomDataObject}{\param{const wxDataFormat\& }{format = wxFormatInvalid}}
 
 The constructor accepts a {\it format} argument which specifies the (single)

-format supported by this object. If it isn't set here,
+format supported by this object. If it isn't set here, 

 \helpref{SetFormat}{wxdataobjectsimplesetformat} should be used.
 
 \membersection{wxCustomDataObject::\destruct{wxCustomDataObject}}\label{wxcustomdataobjectdtor}
 \helpref{SetFormat}{wxdataobjectsimplesetformat} should be used.
 
 \membersection{wxCustomDataObject::\destruct{wxCustomDataObject}}\label{wxcustomdataobjectdtor}