]> git.saurik.com Git - wxWidgets.git/blame - docs/latex/wx/dataobj.tex
added CentreOnScreen(), updated the docs to clear this mess a bit
[wxWidgets.git] / docs / latex / wx / dataobj.tex
CommitLineData
717a57c2
VZ
1%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
2%% Name: dataobj.tex
3%% Purpose: wxDataObject documentation
4%% Author: Vadim Zeitlin
5%% Modified by:
6%% Created: 18.10.99
7%% RCS-ID: $Id$
8%% Copyright: (c) wxWindows team
9%% Licence: wxWindows licence
10%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
11
dface61c
JS
12\section{\class{wxDataObject}}\label{wxdataobject}
13
14A wxDataObject represents data that can be copied to or from the clipboard, or
717a57c2 15dragged and dropped. The important thing about wxDataObject is that this is a
407f3681
JS
16'smart' piece of data unlike usual 'dumb' data containers such as memory
17buffers or files. Being 'smart' here means that the data object itself should
717a57c2
VZ
18know what data formats it supports and how to render itself in each of
19supported formats.
20
21A supported format, incidentally, is exactly the format in which the data can
22be requested from a data object or from which the data object may be set. In
407f3681
JS
23the general case, an object may support different formats on 'input' and
24'output', i.e. it may be able to render itself in a given format but not be
717a57c2
VZ
25created from data on this format or vice versa. wxDataObject defines an
26enumeration type
27
28\begin{verbatim}
29enum Direction
30{
31 Get = 0x01, // format is supported by GetDataHere()
32 Set = 0x02 // format is supported by SetData()
33};
34\end{verbatim}
35
b1462dfa 36which allows to distinguish between them. See
717a57c2
VZ
37\helpref{wxDataFormat}{wxdataformat} documentation for more about formats.
38
407f3681 39Not surprizingly, being 'smart' comes at a price of added complexity. This is
717a57c2
VZ
40reasonable for the situations when you really need to support multiple formats,
41but may be annoying if you only want to do something simple like cut and paste
42text.
43
44To provide a solution for both cases, wxWindows has two predefined classes
b1462dfa
RD
45which derive from wxDataObject: \helpref{wxDataObjectSimple}{wxdataobjectsimple} and
46\helpref{wxDataObjectComposite}{wxdataobjectcomposite}.
717a57c2
VZ
47\helpref{wxDataObjectSimple}{wxdataobjectsimple} is
48the simplest wxDataObject possible and only holds data in a single format (such
49as HTML or text) and \helpref{wxDataObjectComposite}{wxdataobjectcomposite} is
50the simplest way to implement wxDataObject which does support multiple formats
51because it achievs this by simply holding several wxDataObjectSimple objects.
52
53So, you have several solutions when you need a wxDataObject class (and you need
54one as soon as you want to transfer data via the clipboard or drag and drop):
55
c03648c2
VZ
56\begin{twocollist}\itemsep=1cm
57\twocolitem{{\bf 0. Use one of built-in classes}}{You may use wxTextDataObject,
717a57c2 58wxBitmapDataObject or wxFileDataObject in the simplest cases when you only need
407f3681 59to support one format and your data is either text, bitmap or list of files.}
c03648c2 60\twocolitem{{\bf 1. Use wxDataObjectSimple}}{Deriving from wxDataObjectSimple is the simplest
717a57c2
VZ
61solution for custom data - you will only support one format and so probably
62won't be able to communicate with other programs, but data transfer will work
63in your program (or between different copies of it).}
c03648c2 64\twocolitem{{\bf 2. Use wxDataObjectComposite}}{This is a simple but powerful
407f3681 65solution which allows you to support any number of formats (either
717a57c2 66standard or custom if you combine it with the previous solution).}
c03648c2 67\twocolitem{{\bf 3. Use wxDataObject directly}}{This is the solution for
717a57c2
VZ
68maximal flexibility and efficiency, but it also is the most difficult to
69implement.}
70\end{twocollist}
71
407f3681 72Please note that the easiest way to use drag and drop and the clipboard with
717a57c2
VZ
73multiple formats is by using wxDataObjectComposite, but it is not the most
74efficient one as each wxDataObjectSimple would contain the whole data in its
f59d80ca 75respective formats. Now imagine that you want to paste 200 pages of text in
717a57c2
VZ
76your proprietary format, as well as Word, RTF, HTML, Unicode and plain text to
77the clipboard and even today's computers are in trouble. For this case, you
78will have to derive from wxDataObject directly and make it enumerate its
79formats and provide the data in the requested format on demand.
80
81Note that neither the GTK data transfer mechanisms for the clipboard and
f59d80ca 82drag and drop, nor the OLE data transfer copy any data until another application
407f3681 83actually requests the data. This is in contrast to the 'feel' offered to the
717a57c2 84user of a program who would normally think that the data resides in the
407f3681 85clipboard after having pressed 'Copy' - in reality it is only declared to be
717a57c2
VZ
86available.
87
88There are several predefined data object classes derived from
b1462dfa
RD
89wxDataObjectSimple: \helpref{wxFileDataObject}{wxfiledataobject},
90\helpref{wxTextDataObject}{wxtextdataobject} and
717a57c2
VZ
91\helpref{wxBitmapDataObject}{wxbitmapdataobject} which can be used without
92change.
93
874a1686 94You may also derive your own data object classes from
0a2017e0 95\helpref{wxCustomDataObject}{wxcustomdataobject} for user-defined types. The
717a57c2
VZ
96format of user-defined data is given as mime-type string literal, such as
97"application/word" or "image/png". These strings are used as they are under
98Unix (so far only GTK) to identify a format and are translated into their
99Windows equivalent under Win32 (using the OLE IDataObject for data exchange to
407f3681
JS
100and from the clipboard and for drag and drop). Note that the format string
101translation under Windows is not yet finished.
717a57c2 102
874a1686 103\pythonnote{At this time this class is not directly usable from wxPython.
b1462dfa
RD
104Derive a class from \helpref{wxPyDataObjectSimple}{wxdataobjectsimple}
105instead.}
106
717a57c2
VZ
107\wxheading{Virtual functions to override}
108
109Each class derived directly from wxDataObject must override and implement all
110of its functions which are pure virtual in the base class.
111
112The data objects which only render their data or only set it (i.e. work in
b1462dfa 113only one direction), should return 0 from
717a57c2 114\helpref{GetFormatCount}{wxdataobjectgetformatcount}.
f37615d7 115
dface61c
JS
116\wxheading{Derived from}
117
717a57c2 118None
dface61c 119
954b8ae6
JS
120\wxheading{Include files}
121
122<wx/dataobj.h>
123
dface61c
JS
124\wxheading{See also}
125
874a1686
RD
126\helpref{Clipboard and drag and drop overview}{wxdndoverview},
127\helpref{DnD sample}{samplednd},
128\helpref{wxFileDataObject}{wxfiledataobject},
129\helpref{wxTextDataObject}{wxtextdataobject},
130\helpref{wxBitmapDataObject}{wxbitmapdataobject},
131\helpref{wxCustomDataObject}{wxcustomdataobject},
132\helpref{wxDropTarget}{wxdroptarget},
133\helpref{wxDropSource}{wxdropsource},
134\helpref{wxTextDropTarget}{wxtextdroptarget},
717a57c2 135\helpref{wxFileDropTarget}{wxfiledroptarget}
dface61c
JS
136
137\latexignore{\rtfignore{\wxheading{Members}}}
138
139\membersection{wxDataObject::wxDataObject}\label{wxdataobjectwxdataobject}
140
141\func{}{wxDataObject}{\void}
142
143Constructor.
144
145\membersection{wxDataObject::\destruct{wxDataObject}}\label{wxdataobjectdtor}
146
147\func{}{\destruct{wxDataObject}}{\void}
148
149Destructor.
150
717a57c2 151\membersection{wxDataObject::GetAllFormats}\label{wxdataobjectgetallformats}
fc9c7c09 152
407f3681 153\constfunc{virtual void}{GetAllFormats}{ \param{wxDataFormat *}{formats}, \param{Direction}{ dir = Get}}
fc9c7c09 154
b1462dfa 155Copy all supported formats in the given direction to the array pointed to by
407f3681 156{\it formats}. There is enough space for GetFormatCount(dir) formats in it.
fc9c7c09
RR
157
158\membersection{wxDataObject::GetDataHere}\label{wxdataobjectgetdatahere}
159
717a57c2 160\constfunc{virtual bool}{GetDataHere}{\param{const wxDataFormat\&}{ format}, \param{void }{*buf} }
fc9c7c09 161
717a57c2
VZ
162The method will write the data of the format {\it format} in the buffer {\it
163buf} and return TRUE on success, FALSE on failure.
fc9c7c09
RR
164
165\membersection{wxDataObject::GetDataSize}\label{wxdataobjectgetdatasize}
166
167\constfunc{virtual size\_t}{GetDataSize}{\param{const wxDataFormat\&}{ format} }
168
169Returns the data size of the given format {\it format}.
170
717a57c2
VZ
171\membersection{wxDataObject::GetFormatCount}\label{wxdataobjectgetformatcount}
172
173\constfunc{virtual size\_t}{GetFormatCount}{\param{Direction}{ dir = Get}}
174
407f3681 175Returns the number of available formats for rendering or setting the data.
717a57c2 176
fc9c7c09 177\membersection{wxDataObject::GetPreferredFormat}\label{wxdataobjectgetpreferredformat}
f37615d7 178
717a57c2 179\constfunc{virtual wxDataFormat}{GetPreferredFormat}{\param{Direction}{ dir = Get}}
f37615d7 180
407f3681
JS
181Returns the preferred format for either rendering the data (if {\it dir} is {\tt Get},
182its default value) or for setting it. Usually this will be the
717a57c2 183native format of the wxDataObject.
f37615d7 184
fc9c7c09 185\membersection{wxDataObject::SetData}\label{wxdataobjectsetdata}
f37615d7 186
407f3681 187\func{virtual bool}{SetData}{ \param{const wxDataFormat\&}{ format}, \param{size\_t}{ len}, \param{const void }{*buf} }
717a57c2
VZ
188
189Set the data in the format {\it format} of the length {\it len} provided in the
190buffer {\it buf}.
dface61c 191
407f3681 192Returns TRUE on success, FALSE on failure.
dface61c 193