X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/305c49a1a93b6c0b6092f0fe1eb855fdd31c2618..a236aa2058ccf3d36e9cafc20fa7375080c4be50:/docs/latex/wx/dataviewrenderer.tex

diff --git a/docs/latex/wx/dataviewrenderer.tex b/docs/latex/wx/dataviewrenderer.tex
index e84d314b95..ce35b8298c 100644
--- a/docs/latex/wx/dataviewrenderer.tex
+++ b/docs/latex/wx/dataviewrenderer.tex
@@ -16,10 +16,10 @@ Additionally, the user can write own renderers by deriving from
 \helpref{wxDataViewCustomRenderer}{wxdataviewcustomrenderer}.
 
 The {\it wxDataViewCellMode} flag controls, what actions
-the cell data allows. {\it wxDATAVIEW_CELL_ACTIVATABLE}
+the cell data allows. {\it wxDATAVIEW\_CELL\_ACTIVATABLE}
 indicates that the user can double click the cell and
 something will happen (e.g. a window for editing a date
-will pop up). {\it wxDATAVIEW_CELL_EDITABLE} indicates
+will pop up). {\it wxDATAVIEW\_CELL\_EDITABLE} indicates
 that the user can edit the data in-place, i.e. an control
 will show up after a slow click on the cell. This behaviour
 is best known from changing the filename in most file 
@@ -224,15 +224,15 @@ wxDataViewDateRenderer
 
 \section{\class{wxDataViewCustomRenderer}}\label{wxdataviewcustomrenderer}
 
-wxDataViewCustomRenderer has to be derived from if the
-user wants to have a completely new renderer. You
-need to overrode at least \helpref{SetValue}{wxdataviewrenderersetvalue},
+You need to derive a new class from wxDataViewCustomRenderer in
+order to write a new renderer. You need to override at least 
+\helpref{SetValue}{wxdataviewrenderersetvalue},
 \helpref{GetValue}{wxdataviewrenderergetvalue}, 
 \helpref{GetSize}{wxdataviewcustomrenderergetsize}
 and \helpref{Render}{wxdataviewcustomrendererrender}.
 
-If you want your renderer to additionally support in-place
-editing then you also need to override 
+If you want your renderer to support in-place editing then you
+also need to override 
 \helpref{HasEditorCtrl}{wxdataviewcustomrendererhaseditorctrl},
 \helpref{CreateEditorCtrl}{wxdataviewcustomrenderercreateeditorctrl}
 and \helpref{GetValueFromEditorCtrl}{wxdataviewcustomrenderergetvaluefromeditorctrl}.
@@ -270,7 +270,7 @@ indicate that this renderer supports in-place editing.
 
 \membersection{wxDataViewCustomRenderer::CreateEditorCtrl}\label{wxdataviewcustomrenderercreateeditorctrl}
 
-\func{virtual wxControl*}{CreateEditorCtrl} {\param{wxWindow *}{parent}, \param{wxRect }{labelRect}, \param{const wxVariant & }{value}}
+\func{virtual wxControl*}{CreateEditorCtrl}{\param{wxWindow *}{parent}, \param{wxRect }{labelRect}, \param{const wxVariant \& }{value}}
 
 Override this to create the actual editor control once editing
 is about to start. {\it parent} is the parent of the editor
@@ -289,7 +289,7 @@ size of the editor control and {\it value} is its initial value:
 
 \membersection{wxDataViewCustomRenderer::GetValueFromEditorCtrl}\label{wxdataviewcustomrenderergetvaluefromeditorctrl}
 
-\func{virtual bool}{GetValueFromEditorCtrl}{\param{wxControl* }{editor}, \param{wxVariant & }{value}}
+\func{virtual bool}{GetValueFromEditorCtrl}{\param{wxControl* }{editor}, \param{wxVariant \& }{value}}
 
 Overrride this so that the renderer can get the value 
 from the editor control (pointed to by {\it editor}):