1 /////////////////////////////////////////////////////////////////////////////
3 // Purpose: interface of wx*DataObject
4 // Author: wxWidgets team
5 // Licence: wxWindows licence
6 /////////////////////////////////////////////////////////////////////////////
12 A wxDataFormat is an encapsulation of a platform-specific format handle
13 which is used by the system for the clipboard and drag and drop operations.
14 The applications are usually only interested in, for example, pasting data
15 from the clipboard only if the data is in a format the program understands
16 and a data format is something which uniquely identifies this format.
18 On the system level, a data format is usually just a number (@c CLIPFORMAT
19 under Windows or @c Atom under X11, for example) and the standard formats
20 are, indeed, just numbers which can be implicitly converted to wxDataFormat.
21 The standard formats are:
24 @itemdef{wxDF_INVALID,
25 An invalid format - used as default argument for functions taking
26 a wxDataFormat argument sometimes.}
28 Text format (wxString).}
31 @itemdef{wxDF_METAFILE,
32 A metafile (wxMetafile, Windows only).}
33 @itemdef{wxDF_FILENAME,
36 An HTML string. This is currently only valid on Mac and MSW.}
39 As mentioned above, these standard formats may be passed to any function
40 taking wxDataFormat argument because wxDataFormat has an implicit
41 conversion from them (or, to be precise from the type
42 @c wxDataFormat::NativeFormat which is the type used by the underlying
43 platform for data formats).
45 Aside the standard formats, the application may also use custom formats
46 which are identified by their names (strings) and not numeric identifiers.
47 Although internally custom format must be created (or @e registered) first,
48 you shouldn't care about it because it is done automatically the first time
49 the wxDataFormat object corresponding to a given format name is created.
50 The only implication of this is that you should avoid having global
51 wxDataFormat objects with non-default constructor because their
52 constructors are executed before the program has time to perform all
53 necessary initialisations and so an attempt to do clipboard format
54 registration at this time will usually lead to a crash!
59 @see @ref overview_dnd, @ref page_samples_dnd, wxDataObject
65 Constructs a data format object for one of the standard data formats or
66 an empty data object (use SetType() or SetId() later in this case).
69 In wxPerl use Wx::Bitmap->newNative(format).
72 wxDataFormat(wxDataFormatId format
= wxDF_INVALID
);
75 Constructs a data format object for a custom format identified by its
79 In wxPerl use Wx::Bitmap->newUser(format).
82 wxDataFormat(const wxString
& format
);
85 Returns the name of a custom format (this function will fail for a
88 wxString
GetId() const;
91 Returns the platform-specific number identifying the format.
93 wxDataFormatId
GetType() const;
96 Sets the format to be the custom format identified by the given name.
98 void SetId(const wxString
& format
);
101 Sets the format to the given value, which should be one of wxDF_XXX
104 void SetType(wxDataFormatId type
);
107 Returns @true if the formats are different.
109 bool operator !=(const wxDataFormat
& format
) const;
112 Returns @true if the formats are different.
114 bool operator !=(wxDataFormatId format
) const;
117 Returns @true if the formats are equal.
119 bool operator ==(const wxDataFormat
& format
) const;
122 Returns @true if the formats are equal.
124 bool operator ==(wxDataFormatId format
) const;
128 const wxDataFormat wxFormatInvalid
;
134 A wxDataObject represents data that can be copied to or from the clipboard,
135 or dragged and dropped. The important thing about wxDataObject is that this
136 is a 'smart' piece of data unlike 'dumb' data containers such as memory
137 buffers or files. Being 'smart' here means that the data object itself
138 should know what data formats it supports and how to render itself in each
139 of its supported formats.
141 A supported format, incidentally, is exactly the format in which the data
142 can be requested from a data object or from which the data object may be
143 set. In the general case, an object may support different formats on
144 'input' and 'output', i.e. it may be able to render itself in a given
145 format but not be created from data on this format or vice versa.
146 wxDataObject defines the wxDataObject::Direction enumeration type which
147 distinguishes between them.
149 See wxDataFormat documentation for more about formats.
151 Not surprisingly, being 'smart' comes at a price of added complexity. This
152 is reasonable for the situations when you really need to support multiple
153 formats, but may be annoying if you only want to do something simple like
156 To provide a solution for both cases, wxWidgets has two predefined classes
157 which derive from wxDataObject: wxDataObjectSimple and
158 wxDataObjectComposite. wxDataObjectSimple is the simplest wxDataObject
159 possible and only holds data in a single format (such as HTML or text) and
160 wxDataObjectComposite is the simplest way to implement a wxDataObject that
161 does support multiple formats because it achieves this by simply holding
162 several wxDataObjectSimple objects.
164 So, you have several solutions when you need a wxDataObject class (and you
165 need one as soon as you want to transfer data via the clipboard or drag and
168 -# Use one of the built-in classes.
169 - You may use wxTextDataObject, wxBitmapDataObject wxFileDataObject,
170 wxURLDataObject in the simplest cases when you only need to support
171 one format and your data is either text, bitmap or list of files.
172 -# Use wxDataObjectSimple
173 - Deriving from wxDataObjectSimple is the simplest solution for custom
174 data - you will only support one format and so probably won't be able
175 to communicate with other programs, but data transfer will work in
176 your program (or between different instances of it).
177 -# Use wxDataObjectComposite
178 - This is a simple but powerful solution which allows you to support
179 any number of formats (either standard or custom if you combine it
180 with the previous solution).
181 -# Use wxDataObject directly
182 - This is the solution for maximum flexibility and efficiency, but it
183 is also the most difficult to implement.
185 Please note that the easiest way to use drag and drop and the clipboard
186 with multiple formats is by using wxDataObjectComposite, but it is not the
187 most efficient one as each wxDataObjectSimple would contain the whole data
188 in its respective formats. Now imagine that you want to paste 200 pages of
189 text in your proprietary format, as well as Word, RTF, HTML, Unicode and
190 plain text to the clipboard and even today's computers are in trouble. For
191 this case, you will have to derive from wxDataObject directly and make it
192 enumerate its formats and provide the data in the requested format on
195 Note that neither the GTK+ data transfer mechanisms for clipboard and drag
196 and drop, nor OLE data transfer, @e copies any data until another application
197 actually requests the data. This is in contrast to the 'feel' offered to
198 the user of a program who would normally think that the data resides in the
199 clipboard after having pressed 'Copy' - in reality it is only declared to
202 You may also derive your own data object classes from wxCustomDataObject
203 for user-defined types. The format of user-defined data is given as a
204 mime-type string literal, such as "application/word" or "image/png". These
205 strings are used as they are under Unix (so far only GTK+) to identify a
206 format and are translated into their Windows equivalent under Win32 (using
207 the OLE IDataObject for data exchange to and from the clipboard and for
208 drag and drop). Note that the format string translation under Windows is
211 Each class derived directly from wxDataObject must override and implement
212 all of its functions which are pure virtual in the base class. The data
213 objects which only render their data or only set it (i.e. work in only one
214 direction), should return 0 from GetFormatCount().
217 This class is not currently usable from wxPerl; you may use
218 Wx::PlDataObjectSimple instead.
224 @see @ref overview_dnd, @ref page_samples_dnd, wxFileDataObject,
225 wxTextDataObject, wxBitmapDataObject, wxCustomDataObject,
226 wxDropTarget, wxDropSource, wxTextDropTarget, wxFileDropTarget
233 /** Format is supported by GetDataHere() */
236 /** Format is supported by SetData() */
240 Format is supported by both GetDataHere() and SetData()
254 virtual ~wxDataObject();
257 Copies all formats supported in the given direction @a dir to the array
258 pointed to by @a formats.
259 There must be enough space for GetFormatCount(dir) formats in it.
262 In wxPerl this method only takes the @a dir parameter. In scalar
263 context it returns the first format in the list, in list
264 context it returns a list containing all the supported
268 virtual void GetAllFormats(wxDataFormat
* formats
,
269 Direction dir
= Get
) const = 0;
272 The method will write the data of the format @a format to the buffer
273 @a buf. In other words, copy the data from this object in the given
274 format to the supplied buffer. Returns @true on success, @false on
277 virtual bool GetDataHere(const wxDataFormat
& format
, void* buf
) const = 0;
280 Returns the data size of the given format @a format.
282 virtual size_t GetDataSize(const wxDataFormat
& format
) const = 0;
285 Returns the number of available formats for rendering or setting the
288 virtual size_t GetFormatCount(Direction dir
= Get
) const = 0;
291 Returns the preferred format for either rendering the data (if @a dir
292 is @c Get, its default value) or for setting it. Usually this will be
293 the native format of the wxDataObject.
295 virtual wxDataFormat
GetPreferredFormat(Direction dir
= Get
) const = 0;
298 Set the data in the format @a format of the length @a len provided in
299 the buffer @a buf. In other words, copy length bytes of data from the
300 buffer to this data object.
303 The format for which to set the data.
305 The size of data in bytes.
307 Non-@NULL pointer to the data.
309 @true on success, @false on failure.
311 virtual bool SetData(const wxDataFormat
& format
, size_t len
, const void* buf
);
314 Returns true if this format is supported.
316 bool IsSupported(const wxDataFormat
& format
, Direction dir
= Get
) const;
321 @class wxCustomDataObject
323 wxCustomDataObject is a specialization of wxDataObjectSimple for some
324 application-specific data in arbitrary (either custom or one of the
325 standard ones). The only restriction is that it is supposed that this data
326 can be copied bitwise (i.e. with @c memcpy()), so it would be a bad idea to
327 make it contain a C++ object (though C struct is fine).
329 By default, wxCustomDataObject stores the data inside in a buffer. To put
330 the data into the buffer you may use either SetData() or TakeData()
331 depending on whether you want the object to make a copy of data or not.
333 This class may be used as is, but if you don't want store the data inside
334 the object but provide it on demand instead, you should override GetSize(),
335 GetData() and SetData() (or may be only the first two or only the last one
336 if you only allow reading/writing the data).
343 class wxCustomDataObject
: public wxDataObjectSimple
347 The constructor accepts a @a format argument which specifies the
348 (single) format supported by this object. If it isn't set here,
349 wxDataObjectSimple::SetFormat() should be used.
351 wxCustomDataObject(const wxDataFormat
& format
= wxFormatInvalid
);
354 The destructor will free the data held by the object. Notice that
355 although it calls the virtual Free() function, the base class version
356 will always be called (C++ doesn't allow calling virtual functions from
357 constructors or destructors), so if you override Free(), you should
358 override the destructor in your class as well (which would probably
359 just call the derived class' version of Free()).
361 virtual ~wxCustomDataObject();
364 This function is called to allocate @a size bytes of memory from
365 SetData(). The default version just uses the operator new.
367 virtual void* Alloc(size_t size
);
370 This function is called when the data is freed, you may override it to
371 anything you want (or may be nothing at all). The default version calls
372 operator delete[] on the data.
377 Returns a pointer to the data.
379 virtual void* GetData() const;
382 Returns the data size in bytes.
384 virtual size_t GetSize() const;
387 Set the data. The data object will make an internal copy.
389 virtual bool SetData(size_t size
, const void* data
);
392 Like SetData(), but doesn't copy the data - instead the object takes
393 ownership of the pointer.
395 void TakeData(size_t size
, void* data
);
401 @class wxDataObjectComposite
403 wxDataObjectComposite is the simplest wxDataObject derivation which may be
404 used to support multiple formats. It contains several wxDataObjectSimple
405 objects and supports any format supported by at least one of them. Only one
406 of these data objects is @e preferred (the first one if not explicitly
407 changed by using the second parameter of Add()) and its format determines
408 the preferred format of the composite data object as well.
410 See wxDataObject documentation for the reasons why you might prefer to use
411 wxDataObject directly instead of wxDataObjectComposite for efficiency
414 This example shows how a composite data object capable of storing either
415 bitmaps or file names (presumably of bitmap files) can be initialized and
419 MyDropTarget::MyDropTarget()
421 wxDataObjectComposite* dataobj = new wxDataObjectComposite();
422 dataobj->Add(new wxBitmapDataObject(), true);
423 dataobj->Add(new wxFileDataObject());
424 SetDataObject(dataobj);
427 wxDragResult MyDropTarget::OnData(wxCoord x, wxCoord y,
428 wxDragResult defaultDragResult)
430 wxDragResult dragResult = wxDropTarget::OnData(x, y, defaultDragResult);
431 if ( dragResult == defaultDragResult )
433 wxDataObjectComposite *
434 dataobjComp = static_cast<wxDataObjectComposite *>(GetDataObject());
436 wxDataFormat format = dataObjects->GetReceivedFormat();
437 wxDataObject *dataobj = dataobjComp->GetObject(format);
438 switch ( format.GetType() )
443 dataobjBitmap = static_cast<wxBitmapDataObject *>(dataobj);
445 ... use dataobj->GetBitmap() ...
452 dataobjFile = static_cast<wxFileDataObject *>(dataobj);
454 ... use dataobj->GetFilenames() ...
459 wxFAIL_MSG( "unexpected data object format" );
470 @see @ref overview_dnd, wxDataObject, wxDataObjectSimple, wxFileDataObject,
471 wxTextDataObject, wxBitmapDataObject
473 class wxDataObjectComposite
: public wxDataObject
477 The default constructor.
479 wxDataObjectComposite();
482 Adds the @a dataObject to the list of supported objects and it becomes
483 the preferred object if @a preferred is @true.
485 void Add(wxDataObjectSimple
* dataObject
, bool preferred
= false);
488 Report the format passed to the SetData() method. This should be the
489 format of the data object within the composite that received data from
490 the clipboard or the DnD operation. You can use this method to find
491 out what kind of data object was received.
493 wxDataFormat
GetReceivedFormat() const;
496 Returns the pointer to the object which supports the passed format for
497 the specified direction.
499 @NULL is returned if the specified @a format is not supported for this
500 direction @a dir. The returned pointer is owned by wxDataObjectComposite
501 itself and shouldn't be deleted by caller.
505 wxDataObjectSimple
*GetObject(const wxDataFormat
& format
,
506 wxDataObject::Direction dir
= wxDataObject::Get
) const;
512 @class wxDataObjectSimple
514 This is the simplest possible implementation of the wxDataObject class.
515 The data object of (a class derived from) this class only supports
516 <strong>one format</strong>, so the number of virtual functions to
517 be implemented is reduced.
519 Notice that this is still an abstract base class and cannot be used
520 directly, it must be derived. The objects supporting rendering the data
521 must override GetDataSize() and GetDataHere() while the objects which may
522 be set must override SetData(). Of course, the objects supporting both
523 operations must override all three methods.
526 In wxPerl, you need to derive your data object class from
527 Wx::PlDataObjectSimple.
533 @see @ref overview_dnd, @ref page_samples_dnd, wxFileDataObject,
534 wxTextDataObject, wxBitmapDataObject
536 class wxDataObjectSimple
: public wxDataObject
540 Constructor accepts the supported format (none by default) which may
541 also be set later with SetFormat().
543 wxDataObjectSimple(const wxDataFormat
& format
= wxFormatInvalid
);
546 Copy the data to the buffer, return @true on success.
547 Must be implemented in the derived class if the object supports rendering
550 virtual bool GetDataHere(void* buf
) const;
553 Gets the size of our data. Must be implemented in the derived class if
554 the object supports rendering its data.
556 virtual size_t GetDataSize() const;
559 Returns the (one and only one) format supported by this object.
560 It is assumed that the format is supported in both directions.
562 const wxDataFormat
& GetFormat() const;
565 Copy the data from the buffer, return @true on success.
566 Must be implemented in the derived class if the object supports setting
569 virtual bool SetData(size_t len
, const void* buf
);
572 Sets the supported format.
574 void SetFormat(const wxDataFormat
& format
);
580 @class wxBitmapDataObject
582 wxBitmapDataObject is a specialization of wxDataObject for bitmap data. It
583 can be used without change to paste data into the wxClipboard or a
584 wxDropSource. A user may wish to derive a new class from this class for
585 providing a bitmap on-demand in order to minimize memory consumption when
586 offering data in several formats, such as a bitmap and GIF.
588 This class may be used as is, but GetBitmap() may be overridden to increase
594 @see @ref overview_dnd, wxDataObject, wxDataObjectSimple, wxFileDataObject,
595 wxTextDataObject, wxDataObject
597 class wxBitmapDataObject
: public wxDataObjectSimple
601 Constructor, optionally passing a bitmap (otherwise use SetBitmap()
604 wxBitmapDataObject(const wxBitmap
& bitmap
= wxNullBitmap
);
607 Returns the bitmap associated with the data object. You may wish to
608 override this method when offering data on-demand, but this is not
609 required by wxWidgets' internals. Use this method to get data in bitmap
610 form from the wxClipboard.
612 virtual wxBitmap
GetBitmap() const;
615 Sets the bitmap associated with the data object. This method is called
616 when the data object receives data. Usually there will be no reason to
617 override this function.
619 virtual void SetBitmap(const wxBitmap
& bitmap
);
625 @class wxURLDataObject
627 wxURLDataObject is a wxDataObject containing an URL and can be used e.g.
628 when you need to put an URL on or retrieve it from the clipboard:
631 wxTheClipboard->SetData(new wxURLDataObject(url));
634 @note This class is derived from wxDataObjectComposite on Windows rather
635 than wxTextDataObject on all other platforms.
640 @see @ref overview_dnd, wxDataObject
642 class wxURLDataObject
: public wxTextDataObject
646 Constructor, may be used to initialize the URL. If @a url is empty,
647 SetURL() can be used later.
649 wxURLDataObject(const wxString
& url
= wxEmptyString
);
652 Returns the URL stored by this object, as a string.
654 wxString
GetURL() const;
657 Sets the URL stored by this object.
659 void SetURL(const wxString
& url
);
664 @class wxTextDataObject
666 wxTextDataObject is a specialization of wxDataObjectSimple for text data.
667 It can be used without change to paste data into the wxClipboard or a
668 wxDropSource. A user may wish to derive a new class from this class for
669 providing text on-demand in order to minimize memory consumption when
670 offering data in several formats, such as plain text and RTF because by
671 default the text is stored in a string in this class, but it might as well
672 be generated when requested. For this, GetTextLength() and GetText() will
673 have to be overridden.
675 Note that if you already have the text inside a string, you will not
676 achieve any efficiency gain by overriding these functions because copying
677 wxStrings is already a very efficient operation (data is not actually
678 copied because wxStrings are reference counted).
683 @see @ref overview_dnd, wxDataObject, wxDataObjectSimple, wxFileDataObject,
686 class wxTextDataObject
: public wxDataObjectSimple
690 Constructor, may be used to initialise the text (otherwise SetText()
691 should be used later).
693 wxTextDataObject(const wxString
& text
= wxEmptyString
);
696 Returns the text associated with the data object. You may wish to
697 override this method when offering data on-demand, but this is not
698 required by wxWidgets' internals. Use this method to get data in text
699 form from the wxClipboard.
701 virtual wxString
GetText() const;
704 Returns the data size. By default, returns the size of the text data
705 set in the constructor or using SetText(). This can be overridden to
706 provide text size data on-demand. It is recommended to return the text
707 length plus 1 for a trailing zero, but this is not strictly required.
709 virtual size_t GetTextLength() const;
712 Returns 2 under wxMac and wxGTK, where text data coming from the
713 clipboard may be provided as ANSI (@c wxDF_TEXT) or as Unicode text
714 (@c wxDF_UNICODETEXT, but only when @c wxUSE_UNICODE==1).
716 Returns 1 under other platforms (e.g. wxMSW) or when building in ANSI mode
717 (@c wxUSE_UNICODE==0).
719 virtual size_t GetFormatCount(wxDataObject::Direction dir
= wxDataObject::Get
) const;
722 Returns the preferred format supported by this object.
724 This is @c wxDF_TEXT or @c wxDF_UNICODETEXT depending on the platform
725 and from the build mode (i.e. from @c wxUSE_UNICODE).
727 const wxDataFormat
& GetFormat() const;
730 Returns all the formats supported by wxTextDataObject.
732 Under wxMac and wxGTK they are @c wxDF_TEXT and @c wxDF_UNICODETEXT,
733 under other ports returns only one of the two, depending on the build mode.
735 virtual void GetAllFormats(wxDataFormat
* formats
,
736 wxDataObject::Direction dir
= wxDataObject::Get
) const;
739 Sets the text associated with the data object. This method is called
740 when the data object receives the data and, by default, copies the text
741 into the member variable. If you want to process the text on the fly
742 you may wish to override this function.
744 virtual void SetText(const wxString
& strText
);
750 @class wxFileDataObject
752 wxFileDataObject is a specialization of wxDataObject for file names. The
753 program works with it just as if it were a list of absolute file names, but
754 internally it uses the same format as Explorer and other compatible
755 programs under Windows or GNOME/KDE filemanager under Unix which makes it
756 possible to receive files from them using this class.
758 @warning Under all non-Windows platforms this class is currently
759 "input-only", i.e. you can receive the files from another
760 application, but copying (or dragging) file(s) from a wxWidgets
761 application is not currently supported. PS: GTK2 should work as
767 @see wxDataObject, wxDataObjectSimple, wxTextDataObject,
768 wxBitmapDataObject, wxDataObject
770 class wxFileDataObject
: public wxDataObjectSimple
779 Adds a file to the file list represented by this data object (Windows only).
781 void AddFile(const wxString
& file
);
784 Returns the array of file names.
786 const wxArrayString
& GetFilenames() const;
790 @class wxHTMLDataObject
792 wxHTMLDataObject is used for working with HTML-formatted text.
797 @see wxDataObject, wxDataObjectSimple
799 class wxHTMLDataObject
: public wxDataObjectSimple
805 wxHTMLDataObject(const wxString
& html
= wxEmptyString
);
808 Returns the HTML string.
810 virtual wxString
GetHTML() const;
813 Sets the HTML string.
815 virtual void SetHTML(const wxString
& html
);