Removed wxImageList overview, and other @ref fixes.

[wxWidgets.git] / docs / doxygen / overviews / dnd.h

diff --git a/docs/doxygen/overviews/dnd.h b/docs/doxygen/overviews/dnd.h
index 0a8c6ece37d83e1da141a0c770fbc73aae456b74..2460afaf6cb5a5c9cd69caff6105df21a31b089b 100644 (file)
--- a/docs/doxygen/overviews/dnd.h
+++ b/docs/doxygen/overviews/dnd.h
@@ -10,19 +10,19 @@
 
  @page overview_dnd Drag and drop overview
 
 
  @page overview_dnd Drag and drop overview
 

- Classes: #wxDataObject, #wxTextDataObject, #wxDropSource, #wxDropTarget,
-          #wxTextDropTarget, #wxFileDropTarget
+ Classes: wxDataObject, wxTextDataObject, wxDropSource, wxDropTarget,
+          wxTextDropTarget, wxFileDropTarget

 
  Note that @c wxUSE_DRAG_AND_DROP must be defined in @c setup.h in order
  to use drag and drop in wxWidgets.
 
 
  Note that @c wxUSE_DRAG_AND_DROP must be defined in @c setup.h in order
  to use drag and drop in wxWidgets.
 

- See also: @ref overview_dataobject and @ref samplednd_overview.
+ See also: @ref overview_dataobject and @ref page_utils_samples_dnd.

 
  It may be noted that data transfer to and from the clipboard is quite
  similar to data transfer with drag and drop and the code to implement
  these two types is almost the same. In particular, both data transfer
 
  It may be noted that data transfer to and from the clipboard is quite
  similar to data transfer with drag and drop and the code to implement
  these two types is almost the same. In particular, both data transfer

- mechanisms store data in some kind of #wxDataObject and identify its format(s)
- using the #wxDataFormat class.
+ mechanisms store data in some kind of wxDataObject and identify its format(s)
+ using the wxDataFormat class.

 
  To be a @e drag source, i.e. to provide the data which may be dragged by
  the user elsewhere, you should implement the following steps:
 
  To be a @e drag source, i.e. to provide the data which may be dragged by
  the user elsewhere, you should implement the following steps:


@@ -44,14 +44,14 @@
      @endcode
 
  @li @b Dragging: The call to DoDragDrop() blocks the program until the user releases 
      @endcode
 
  @li @b Dragging: The call to DoDragDrop() blocks the program until the user releases 

-     the mouse button (unless you override the #GiveFeedback function to do something 
-     special). When the mouse moves in a window of a program which understands the
-     same drag-and-drop protocol (any program under Windows or any program supporting
-     the XDnD protocol under X Windows), the corresponding #wxDropTarget methods
+     the mouse button (unless you override the wxDropSource::GiveFeedback function to 
+     do something special). When the mouse moves in a window of a program which understands
+     the same drag-and-drop protocol (any program under Windows or any program supporting
+     the XDnD protocol under X Windows), the corresponding wxDropTarget methods

      are called - see below.
 
  @li <b>Processing the result</b>: DoDragDrop() returns an @e effect code which
      are called - see below.
 
  @li <b>Processing the result</b>: DoDragDrop() returns an @e effect code which

-     is one of the values of @c wxDragResult enum (explained #here):
+     is one of the values of @c wxDragResult enum (explained in wxDropTarget page):

 
      @code
      switch (result)
 
      @code
      switch (result)


@@ -73,18 +73,18 @@
  follow the instructions below:
 
  @li @b Initialization: For a window to be a drop target, it needs to have
  follow the instructions below:
 
  @li @b Initialization: For a window to be a drop target, it needs to have

-     an associated #wxDropTarget object. Normally, you will call wxWindow::SetDropTarget 
-     during window creation associating your drop target with it. You must derive a class from
-     wxDropTarget and override its pure virtual methods. Alternatively, you may
-     derive from #wxTextDropTarget or #wxFileDropTarget and override their OnDropText()
+     an associated wxDropTarget object. Normally, you will call wxWindow::SetDropTarget 
+     during window creation associating your drop target with it. You must derive a class
+     from wxDropTarget and override its pure virtual methods. Alternatively, you may
+     derive from wxTextDropTarget or wxFileDropTarget and override their OnDropText()

      or OnDropFiles() method.
 
  @li @b Drop: When the user releases the mouse over a window, wxWidgets
      asks the associated wxDropTarget object if it accepts the data. For this,
      or OnDropFiles() method.
 
  @li @b Drop: When the user releases the mouse over a window, wxWidgets
      asks the associated wxDropTarget object if it accepts the data. For this,

-     a #wxDataObject must be associated with the drop target and this data object will
+     a wxDataObject must be associated with the drop target and this data object will

      be responsible for the format negotiation between the drag source and the drop target.
      be responsible for the format negotiation between the drag source and the drop target.

-     If all goes well, then #OnData will get called and the wxDataObject belonging to 
-     the drop target can get filled with data.
+     If all goes well, then wxDropTarget::OnData will get called and the wxDataObject belonging 
+     to the drop target can get filled with data.

 
  @li <b>The end</b>: After processing the data, DoDragDrop() returns either
      wxDragCopy or wxDragMove depending on the state of the keys Ctrl, Shift
 
  @li <b>The end</b>: After processing the data, DoDragDrop() returns either
      wxDragCopy or wxDragMove depending on the state of the keys Ctrl, Shift