summaryrefslogtreecommitdiff
path: root/documentation/events.html
diff options
context:
space:
mode:
authorMatthias Melcher <fltk@matthiasm.com>2002-02-24 21:09:51 +0000
committerMatthias Melcher <fltk@matthiasm.com>2002-02-24 21:09:51 +0000
commit2cde58f966908851c8d97ee442cdbf825c180899 (patch)
treecd71c3ec57878cd4accc902b7c1795a850ef0d55 /documentation/events.html
parent4603756ed1284dfc9d71a556976f4f5b898abd24 (diff)
Update documentation to contain DND stuff.
I am missing a decent Linux machine. Could someone please check if DND works smoothly on those machines? Just run the 'Input' test and mark and drag text out of the text widgets into another app. Then drag'n'drop text into the FLTK widgets. Finally drag text from one widget into another widget within the same FLTK app. git-svn-id: file:///fltk/svn/fltk/branches/branch-1.1@1972 ea41ed52-d2ee-0310-a9c1-e6b18d33e121
Diffstat (limited to 'documentation/events.html')
-rw-r--r--documentation/events.html24
1 files changed, 24 insertions, 0 deletions
diff --git a/documentation/events.html b/documentation/events.html
index a742d69f4..c9921f818 100644
--- a/documentation/events.html
+++ b/documentation/events.html
@@ -217,6 +217,30 @@ widget. This indicates that some other widget or program has
claimed the selection. Motif programs used this to clear the
selection indication. Most modern programs ignore this.
+<H2><A NAME="dnd">Drag And Drop Events</A></H2>
+
+<H3>FL_DND_ENTER</H3>
+
+<P>The mouse has been moved to point at this widget. A widget
+that is interested in receiving drag'n'drop data must return 1
+to receive FL_DND_DRAG, FL_DND_LEAVE and FL_DND_RELEASE events.
+
+<H3>FL_DND_DRAG</H3>
+
+<P>The mouse has been moved inside a widget while dragging data.
+A widget that is interested in receiving drag'n'drop data should
+indicate the possible drop position.
+
+<H3>FL_DND_LEAVE</H3>
+
+<P>The mouse has moved out of the widget.
+
+<H3>FL_DND_RELEASE</H3>
+
+<P>The user has released the mouse button dropping data into
+the widget. If the widget returns 1, it will receive the data in
+the immediatly following FL_PASTE event.
+
<H2><A name="event_xxx">Fl::event_*() methods</A></H2>
<P>FLTK keeps the information about the most recent event in