X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/a3ab1c18017bb08329e73918f9f502ea00cdb447..65dd9ae23c1532fbbd43c19dccd7cc8a25a8a6f4:/docs/latex/wx/trefcount.tex?ds=sidebyside

diff --git a/docs/latex/wx/trefcount.tex b/docs/latex/wx/trefcount.tex
index c051acc1b1..01ed32c0a1 100644
--- a/docs/latex/wx/trefcount.tex
+++ b/docs/latex/wx/trefcount.tex
@@ -18,7 +18,6 @@ transparently to the class users and that whether an object is shared or not
 is not seen from the outside of the class - in any case, the result of any
 operation on it is the same.
 
-\subsection{List of reference-counted wxWidgets classes}\label{refcountlist}
 \subsection{Object comparison}\label{refcountequality}
 
 The $==$ and $!=$ operators of \helpref{wxWidgets COW objects}{refcountlist}
@@ -48,6 +47,8 @@ destroyed. As for all other COW-things, this happens transparently to the class
 that you shouldn't care about it.
 
 
+\subsection{List of reference-counted wxWidgets classes}\label{refcountlist}
+
 The following classes in wxWidgets have efficient (i.e. fast) assignment operators
 and copy constructors since they are reference-counted:
 
@@ -63,14 +64,17 @@ and copy constructors since they are reference-counted:
 \helpref{wxPalette}{wxpalette}\\
 \helpref{wxPen}{wxpen}\\
 \helpref{wxRegion}{wxregion}\\
-\helpref{wxString}{wxstring}
+\helpref{wxString}{wxstring}\\
+\helpref{wxVariant}{wxvariant}\\
+\helpref{wxVariantData}{wxvariantdata}
 
 Note that the list above reports the objects which are reference-counted in all ports of
 wxWidgets; some ports may use this tecnique also for other classes.
 \subsection{Make your own reference-counted class}\label{wxobjectoverview}
 
 Reference counting can be implemented easily using \helpref{wxObject}{wxobject}
-and \helpref{wxObjectRefData}{wxobjectrefdata} classes.
+and \helpref{wxObjectRefData}{wxobjectrefdata} classes. Alternatively, you
+can also use the \helpref{wxObjectDataPtr<T>}{wxobjectdataptr} template.
 
 First, derive a new class from \helpref{wxObjectRefData}{wxobjectrefdata} and
 put there the memory-consuming data.