diff options
| author | Michael R Sweet <michael.r.sweet@gmail.com> | 2001-09-30 20:25:36 +0000 |
|---|---|---|
| committer | Michael R Sweet <michael.r.sweet@gmail.com> | 2001-09-30 20:25:36 +0000 |
| commit | 2c61d60470b0583614437950066b2f63c4ac2782 (patch) | |
| tree | f32ab07a4acdbfca9f3389ec851dc5c4b9e09653 /documentation/events.html | |
| parent | eb9a83b3483608286be0a9ead6b98938d21370f3 (diff) | |
Documentation updates.
git-svn-id: file:///fltk/svn/fltk/branches/branch-1.1@1625 ea41ed52-d2ee-0310-a9c1-e6b18d33e121
Diffstat (limited to 'documentation/events.html')
| -rw-r--r-- | documentation/events.html | 20 |
1 files changed, 10 insertions, 10 deletions
diff --git a/documentation/events.html b/documentation/events.html index 12072d73a..2eb847545 100644 --- a/documentation/events.html +++ b/documentation/events.html @@ -9,7 +9,7 @@ a key, an event is generated and sent to your application. Events can also come from other programs like the window manager. <P>Events are identified by the integer argument passed to the -<A href=functions.html#handle> <TT>Fl_Widget::handle()</TT></A> virtual +<A href="subclassing.html#handle"> <TT>Fl_Widget::handle()</TT></A> virtual method. Other information about the most recent event is stored in static locations and acquired by calling the <A href=#event_xxx><TT>Fl::event_*()</TT></A> methods. This static @@ -20,28 +20,28 @@ method). <H2>Mouse Events</H2> <H3>FL_PUSH</H3> A mouse button has gone down with the mouse pointing at this widget. -You can find out what button by calling <A href=#event_button><TT> +You can find out what button by calling <A href="functions.html#event_button"><TT> Fl::event_button()</TT></A>. You find out the mouse position by -calling <A href=#event_x><TT>Fl::event_x()</TT></A> and <A href=functions.html#event_y> +calling <A href="functions.html#event_x"><TT>Fl::event_x()</TT></A> and <A href="functions.html#event_y"> <TT>Fl::event_y()</TT></A>. <P>A widget indicates that it "wants" the mouse click by returning -non-zero from its <A href=functions.html#handle><TT>handle()</TT></A> - method. It will then become the <A href=functions.html#pushed><TT> +non-zero from its <A href="subclassing.html#handle"><TT>handle()</TT></A> + method. It will then become the <A href="functions.html#pushed"><TT> Fl::pushed()</TT></A> widget and will get <TT>FL_DRAG</TT> and the matching <TT>FL_RELEASE</TT> events. If <TT>handle()</TT> returns zero then FLTK will try sending the <TT>FL_PUSH</TT> to another widget. </P> <H3>FL_DRAG</H3> The mouse has moved with a button held down. The current button state is -in <a href="#event_state"><tt>Fl::event_state()</tt></a>. The mouse position -is in <a href="#event_x"><tt>Fl::event_x()</tt></a> and -<a href="#event_y"><tt>Fl::event_y()</tt></a>. +in <a href="functions.html#event_state"><tt>Fl::event_state()</tt></a>. The mouse position +is in <a href="functions.html#event_x"><tt>Fl::event_x()</tt></a> and +<a href="functions.html#event_y"><tt>Fl::event_y()</tt></a>. <P>To receive <CODE>FL_DRAG</CODE> events you must also respond to the <CODE>FL_PUSH</CODE> and <CODE>FL_RELEASE</CODE> events. <H3>FL_RELEASE</H3> A mouse button has been released. You can find out what button by -calling <A href=#event_button><TT>Fl::event_button()</TT></A>. +calling <A href="functions.html#event_button"><TT>Fl::event_button()</TT></A>. <H3>FL_MOVE</H3> The mouse has moved without any mouse buttons held down. This event is sent to the <A href="functions.html#belowmouse"><TT>Fl::belowmouse()</TT></A> @@ -187,7 +187,7 @@ to leaf widgets. These procedures control those leaf widgets: </P> <LI><A href=functions.html#grab><TT>Fl::grab</TT></A></LI> <LI><A href=functions.html#modal><TT>Fl::modal</TT></A></LI> <LI><A href=functions.html#pushed><TT>Fl::pushed</TT></A></LI> -<LI><A href=functions.html#release><TT>Fl::release</TT></A></LI> +<LI><TT>Fl::release</TT></LI> <LI><A href=Fl_Widget.html#Fl_Widget.take_focus><TT>Fl_Widget::take_focus</TT></A> </LI> </UL> |