fix for wxExecute(subprocess which produces a lot of output) bug

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

diff --git a/docs/latex/wx/object.tex b/docs/latex/wx/object.tex
index 1cce58e408917ff84a86b3ace116b680db886f3c..a93d8e02d1919886e98070b6165b7b4ad2013a6d 100644 (file)
--- a/docs/latex/wx/object.tex
+++ b/docs/latex/wx/object.tex
@@ -48,6 +48,13 @@ Pointer to an object which is the object's reference-counted data.
 \helpref{wxObject::GetRefData}{wxobjectgetrefdata},\rtfsp
 \helpref{wxObjectRefData}{wxobjectrefdata}
 
 \helpref{wxObject::GetRefData}{wxobjectgetrefdata},\rtfsp
 \helpref{wxObjectRefData}{wxobjectrefdata}
 

+\membersection{wxObject::CopyObject}\label{wxobjectcopyobject}
+
+\func{virtual void}{CopyObject}{\param{wxObject\&}{ object\_dest}}
+
+Create a copy of this object in object\_dest. Must perform a full copy of self
+so that object\_dest will be valid after this object is deleted
+

 \membersection{wxObject::Dump}\label{wxobjectdump}
 
 \func{void}{Dump}{\param{ostream\&}{ stream}}
 \membersection{wxObject::Dump}\label{wxobjectdump}
 
 \func{void}{Dump}{\param{ostream\&}{ stream}}


@@ -65,8 +72,8 @@ Currently wxWindows does not define Dump for derived classes, but
 programmers may wish to use it for their own applications. Be sure to
 call the Dump member of the class's base class to allow all information to be dumped.
 
 programmers may wish to use it for their own applications. Be sure to
 call the Dump member of the class's base class to allow all information to be dumped.
 

-The implementation of this function just writes the class name of the object.
-If DEBUG is undefined or zero, the implementation is empty.
+The implementation of this function just writes the class name of the object
+in debug build (\_\_WXDEBUG\_\_ defined), otherwise it does nothing.

 
 \membersection{wxObject::GetClassInfo}\label{wxobjectgetclassinfo}
 
 
 \membersection{wxObject::GetClassInfo}\label{wxobjectgetclassinfo}
 


@@ -164,7 +171,7 @@ The {\bf m\_refData} member is set to NULL.
 \func{void *}{new}{\param{size\_t }{size}, \param{const wxString\& }{filename = NULL}, \param{int}{ lineNum = 0}}
 
 The {\it new} operator is defined for debugging versions of the library only, when
 \func{void *}{new}{\param{size\_t }{size}, \param{const wxString\& }{filename = NULL}, \param{int}{ lineNum = 0}}
 
 The {\it new} operator is defined for debugging versions of the library only, when

-the identifier DEBUG is defined and is more than zero. It takes over memory allocation, allowing
+the identifier \_\_WXDEBUG\_\_ is defined. It takes over memory allocation, allowing

 wxDebugContext operations.
 
 \membersection{wxObject::operator delete}\label{wxobjectdelete}
 wxDebugContext operations.
 
 \membersection{wxObject::operator delete}\label{wxobjectdelete}


@@ -172,7 +179,7 @@ wxDebugContext operations.
 \func{void}{delete}{\param{void }{buf}}
 
 The {\it delete} operator is defined for debugging versions of the library only, when
 \func{void}{delete}{\param{void }{buf}}
 
 The {\it delete} operator is defined for debugging versions of the library only, when

-the identifier DEBUG is defined and is more than zero. It takes over memory deallocation, allowing
+the identifier \_\_WXDEBUG\_\_ is defined. It takes over memory deallocation, allowing

 wxDebugContext operations.
 
 \section{\class{wxObjectRefData}}\label{wxobjectrefdata}
 wxDebugContext operations.
 
 \section{\class{wxObjectRefData}}\label{wxobjectrefdata}