Fixes to Cygwin/Mingw32 makefile, manual now compiles wxStaticLine, etc.

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

diff --git a/docs/latex/wx/dataobj.tex b/docs/latex/wx/dataobj.tex
index 2538703aaffc119376cea353a089c41fe5c017c2..3e5cf060cc4b37b232799a5f8792735312a05ad8 100644 (file)
--- a/docs/latex/wx/dataobj.tex
+++ b/docs/latex/wx/dataobj.tex
@@ -33,7 +33,7 @@ enum Direction
 };
 \end{verbatim}
 
 };
 \end{verbatim}
 

-which allows to distinguish between them. See 
+which allows to distinguish between them. See

 \helpref{wxDataFormat}{wxdataformat} documentation for more about formats.
 
 Not surprizingly, being 'smart' comes at a price of added complexity. This is
 \helpref{wxDataFormat}{wxdataformat} documentation for more about formats.
 
 Not surprizingly, being 'smart' comes at a price of added complexity. This is


@@ -42,8 +42,8 @@ but may be annoying if you only want to do something simple like cut and paste
 text.
 
 To provide a solution for both cases, wxWindows has two predefined classes
 text.
 
 To provide a solution for both cases, wxWindows has two predefined classes

-which derive from wxDataObject: \helpref{wxDataObjectSimple}{wxdataobjectsimple} and 
-\helpref{wxDataObjectComposite}{wxdataobjectcomposite}. 
+which derive from wxDataObject: \helpref{wxDataObjectSimple}{wxdataobjectsimple} and
+\helpref{wxDataObjectComposite}{wxdataobjectcomposite}.

 \helpref{wxDataObjectSimple}{wxdataobjectsimple} is
 the simplest wxDataObject possible and only holds data in a single format (such
 as HTML or text) and \helpref{wxDataObjectComposite}{wxdataobjectcomposite} is
 \helpref{wxDataObjectSimple}{wxdataobjectsimple} is
 the simplest wxDataObject possible and only holds data in a single format (such
 as HTML or text) and \helpref{wxDataObjectComposite}{wxdataobjectcomposite} is


@@ -53,18 +53,18 @@ because it achievs this by simply holding several wxDataObjectSimple objects.
 So, you have several solutions when you need a wxDataObject class (and you need
 one as soon as you want to transfer data via the clipboard or drag and drop):
 
 So, you have several solutions when you need a wxDataObject class (and you need
 one as soon as you want to transfer data via the clipboard or drag and drop):
 

-\begin{twocollist}\itemsep=0pt
-\twocolitem{0. Use one of built-in classes}{You may use wxTextDataObject,
+\begin{twocollist}\itemsep=1cm
+\twocolitem{{\bf 0. Use one of built-in classes}}{You may use wxTextDataObject,

 wxBitmapDataObject or wxFileDataObject in the simplest cases when you only need
 to support one format and your data is either text, bitmap or list of files.}
 wxBitmapDataObject or wxFileDataObject in the simplest cases when you only need
 to support one format and your data is either text, bitmap or list of files.}

-\twocolitem{1. Derive your class from wxDataObjectSimple}{This is the simplest
+\twocolitem{{\bf 1. Use wxDataObjectSimple}}{Deriving from wxDataObjectSimple is the simplest

 solution for custom data - you will only support one format and so probably
 won't be able to communicate with other programs, but data transfer will work
 in your program (or between different copies of it).}
 solution for custom data - you will only support one format and so probably
 won't be able to communicate with other programs, but data transfer will work
 in your program (or between different copies of it).}

-\twocolitem{2. Use wxDataObjectComposite}{This is a simple but powerful
+\twocolitem{{\bf 2. Use wxDataObjectComposite}}{This is a simple but powerful

 solution which allows you to support any number of formats (either
 standard or custom if you combine it with the previous solution).}
 solution which allows you to support any number of formats (either
 standard or custom if you combine it with the previous solution).}

-\twocolitem{3. Derive from wxDataObject directly}{This is the solution for
+\twocolitem{{\bf 3. Use wxDataObject directly}}{This is the solution for

 maximal flexibility and efficiency, but it also is the most difficult to
 implement.}
 \end{twocollist}
 maximal flexibility and efficiency, but it also is the most difficult to
 implement.}
 \end{twocollist}


@@ -86,13 +86,13 @@ clipboard after having pressed 'Copy' - in reality it is only declared to be
 available.
 
 There are several predefined data object classes derived from
 available.
 
 There are several predefined data object classes derived from

-wxDataObjectSimple: \helpref{wxFileDataObject}{wxfiledataobject}, 
-\helpref{wxTextDataObject}{wxtextdataobject} and 
+wxDataObjectSimple: \helpref{wxFileDataObject}{wxfiledataobject},
+\helpref{wxTextDataObject}{wxtextdataobject} and

 \helpref{wxBitmapDataObject}{wxbitmapdataobject} which can be used without
 change.
 
 You may also derive your own data object classes from 
 \helpref{wxBitmapDataObject}{wxbitmapdataobject} which can be used without
 change.
 
 You may also derive your own data object classes from 

-\helpref{wxCustomDataObject}{wxprivatedataobject} for user-defined types. The
+\helpref{wxCustomDataObject}{wxcustomdataobject} for user-defined types. The

 format of user-defined data is given as mime-type string literal, such as
 "application/word" or "image/png". These strings are used as they are under
 Unix (so far only GTK) to identify a format and are translated into their
 format of user-defined data is given as mime-type string literal, such as
 "application/word" or "image/png". These strings are used as they are under
 Unix (so far only GTK) to identify a format and are translated into their


@@ -100,13 +100,17 @@ Windows equivalent under Win32 (using the OLE IDataObject for data exchange to
 and from the clipboard and for drag and drop). Note that the format string
 translation under Windows is not yet finished.
 
 and from the clipboard and for drag and drop). Note that the format string
 translation under Windows is not yet finished.
 

+\pythonnote{At this time this class is directly usable from wxPython.
+Derive a class from \helpref{wxPyDataObjectSimple}{wxdataobjectsimple}
+instead.}
+

 \wxheading{Virtual functions to override}
 
 Each class derived directly from wxDataObject must override and implement all
 of its functions which are pure virtual in the base class.
 
 The data objects which only render their data or only set it (i.e. work in
 \wxheading{Virtual functions to override}
 
 Each class derived directly from wxDataObject must override and implement all
 of its functions which are pure virtual in the base class.
 
 The data objects which only render their data or only set it (i.e. work in

-only one direction), should return 0 from 
+only one direction), should return 0 from

 \helpref{GetFormatCount}{wxdataobjectgetformatcount}.
 
 \wxheading{Derived from}
 \helpref{GetFormatCount}{wxdataobjectgetformatcount}.
 
 \wxheading{Derived from}


@@ -119,12 +123,12 @@ None
 
 \wxheading{See also}
 
 
 \wxheading{See also}
 

-\helpref{Clipboard and drag and drop overview}{wxclipboardonfigoverview}, 
+\helpref{Clipboard and drag and drop overview}{wxdndoverview}, 

 \helpref{DnD sample}{samplednd}, 
 \helpref{wxFileDataObject}{wxfiledataobject}, 
 \helpref{wxTextDataObject}{wxtextdataobject}, 
 \helpref{wxBitmapDataObject}{wxbitmapdataobject}, 
 \helpref{DnD sample}{samplednd}, 
 \helpref{wxFileDataObject}{wxfiledataobject}, 
 \helpref{wxTextDataObject}{wxtextdataobject}, 
 \helpref{wxBitmapDataObject}{wxbitmapdataobject}, 

-\helpref{wxPrivateDataObject}{wxprivatedataobject}, 
+\helpref{wxCustomDataObject}{wxcustomdataobject}, 

 \helpref{wxDropTarget}{wxdroptarget}, 
 \helpref{wxDropSource}{wxdropsource}, 
 \helpref{wxTextDropTarget}{wxtextdroptarget}, 
 \helpref{wxDropTarget}{wxdroptarget}, 
 \helpref{wxDropSource}{wxdropsource}, 
 \helpref{wxTextDropTarget}{wxtextdroptarget}, 


@@ -148,7 +152,7 @@ Destructor.
 
 \constfunc{virtual void}{GetAllFormats}{ \param{wxDataFormat *}{formats}, \param{Direction}{ dir = Get}}
 
 
 \constfunc{virtual void}{GetAllFormats}{ \param{wxDataFormat *}{formats}, \param{Direction}{ dir = Get}}
 

-Copy all supported formats in the given direction to the array pointed to by 
+Copy all supported formats in the given direction to the array pointed to by

 {\it formats}. There is enough space for GetFormatCount(dir) formats in it.
 
 \membersection{wxDataObject::GetDataHere}\label{wxdataobjectgetdatahere}
 {\it formats}. There is enough space for GetFormatCount(dir) formats in it.
 
 \membersection{wxDataObject::GetDataHere}\label{wxdataobjectgetdatahere}