converted more html to plain doxygen in {events,subclassing,opengl}.dox

git-svn-id: file:///fltk/svn/fltk/branches/branch-1.3@6406 ea41ed52-d2ee-0310-a9c1-e6b18d33e121

1 files changed, 202 insertions, 209 deletions

diff --git a/documentation/events.dox b/documentation/events.dox
index 6f4db3c1c..f41628bdf 100644
--- a/documentation/events.dox
+++ b/documentation/events.dox
@@ -2,269 +2,273 @@
 
  \page	events	6 - Handling Events
  
-<P>This chapter discusses the FLTK event model and how to handle
+This chapter discusses the FLTK event model and how to handle
 events in your program or widget.
 
-<H2>The FLTK Event Model</H2>
+\section events_model The FLTK Event Model
 
-<P>Every time a user moves the mouse pointer, clicks a button,
+Every time a user moves the mouse pointer, clicks a button,
 or presses 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="subclassing.html#handle"><TT>Fl_Widget::handle()</TT></A> virtual
+Events are identified by the integer argument passed to the
+<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 \ref events_event_xxx
 methods. This static information remains valid until the next event
 is read from the window system, so it is ok to look at it outside 
-of the <TT>handle()</TT> method.
+of the <tt>handle()</tt> method.
 
-<H2>Mouse Events</H2>
+\section events_mouse Mouse Events
 
-<H3>FL_PUSH</H3>
+\subsection events_fl_push FL_PUSH
 
-<P>A mouse button has gone down with the mouse pointing at this
-widget. You can find out what button by calling <A
-href="Fl.html#Fl.event_button"><TT>
-Fl::event_button()</TT></A>. You find out the mouse position by
-calling <A
-href="Fl.html#Fl.event_x"><TT>Fl::event_x()</TT></A> and <A
-href="Fl.html#Fl.event_y"> <TT>Fl::event_y()</TT></A>.
+A mouse button has gone down with the mouse pointing at this
+widget. You can find out what button by calling
+<A href="Fl.html#Fl.event_button"><tt>Fl::event_button()</tt></A>.
+You find out the mouse position by calling
+<A href="Fl.html#Fl.event_x"><tt>Fl::event_x()</tt></A>
+and
+<A href="Fl.html#Fl.event_y"> <tt>Fl::event_y()</tt></A>.
 
-<P>A widget indicates that it &quot;wants&quot; the mouse click
-by returning non-zero from its <A
-href="subclassing.html#handle"><TT>handle()</TT></A> method. It
-will then become the <A href="Fl.html#Fl.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>
+A widget indicates that it &quot;wants&quot; the mouse click
+by returning non-zero from its
+<A href="subclassing.html#handle"><tt>handle()</tt></A>
+method. It will then become the
+<A href="Fl.html#Fl.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. 
 
-<H3>FL_DRAG</H3>
+\subsection events_fl_drag FL_DRAG
 
-<P>The mouse has moved with a button held down. The current
-button state is in <a
-href="Fl.html#Fl.event_state"><tt>Fl::event_state()</tt></a>.
-The mouse position is in <a
-href="Fl.html#Fl.event_x"><tt>Fl::event_x()</tt></a> and <a
-href="Fl.html#Fl.event_y"><tt>Fl::event_y()</tt></a>.
+The mouse has moved with a button held down. The current
+button state is in
+<a href="Fl.html#Fl.event_state"><tt>Fl::event_state()</tt></a>.
+The mouse position is in
+<a href="Fl.html#Fl.event_x"><tt>Fl::event_x()</tt></a>
+and
+<a href="Fl.html#Fl.event_y"><tt>Fl::event_y()</tt></a>.
 
-<P>In order to receive <TT>FL_DRAG</TT> events, the widget must
-return non-zero when handling <TT>FL_PUSH</TT>.</P>
+In order to receive <tt>FL_DRAG</tt> events, the widget must
+return non-zero when handling <tt>FL_PUSH</tt>.
 
-<H3>FL_RELEASE</H3>
+\subsection events_fl_release FL_RELEASE
 
-<P>A mouse button has been released. You can find out what
-button by calling <A
-href="Fl.html#Fl.event_button"><TT>Fl::event_button()</TT></A>.
+A mouse button has been released. You can find out what button by calling
+<A href="Fl.html#Fl.event_button"><tt>Fl::event_button()</tt></A>.
 
-<P>In order to receive the <TT>FL_RELEASE</TT> event, the widget must
-return non-zero when handling <TT>FL_PUSH</TT>.</P>
+In order to receive the <tt>FL_RELEASE</tt> event, the widget must
+return non-zero when handling <tt>FL_PUSH</tt>.
 
-<H3>FL_MOVE</H3>
+\subsection events_fl_move FL_MOVE
 
-<P>The mouse has moved without any mouse buttons held down. 
-This event is sent to the <A
-href="Fl.html#Fl.belowmouse"><TT>Fl::belowmouse()</TT></A>
-widget.</P>
+The mouse has moved without any mouse buttons held down. 
+This event is sent to the
+<A href="Fl.html#Fl.belowmouse"><tt>Fl::belowmouse()</tt></A>
+widget.
 
-<P>In order to receive <TT>FL_MOVE</TT> events, the widget must
-return non-zero when handling <TT>FL_ENTER</TT>.</P>
+In order to receive <tt>FL_MOVE</tt> events, the widget must
+return non-zero when handling <tt>FL_ENTER</tt>.
 
-<H3>FL_MOUSEWHEEL</H3>
+\subsection events_fl_mousewheel FL_MOUSEWHEEL
 
-<P>The user has moved the mouse wheel. The <A
-HREF="Fl.html#Fl.event_dx"><TT>Fl::event_dx()</TT></A> and <A
-HREF="Fl.html#Fl.event_dy"><TT>Fl::event_dy()</TT></A> methods
-can be used to find the amount to scroll horizontally and
+The user has moved the mouse wheel. The
+<A HREF="Fl.html#Fl.event_dx"><tt>Fl::event_dx()</tt></A>
+and
+<A HREF="Fl.html#Fl.event_dy"><tt>Fl::event_dy()</tt></A>
+methods can be used to find the amount to scroll horizontally and
 vertically.
 
-<H2>Focus Events</H2>
+\section events_focus Focus Events
 
-<H3>FL_ENTER</H3>
+\subsection events_fl_enter FL_ENTER
 
-<P>The mouse has been moved to point at this widget.  This can
+The mouse has been moved to point at this widget.  This can
 be used for highlighting feedback.  If a widget wants to
 highlight or otherwise track the mouse, it indicates this by
-returning non-zero from its <A
-href="Fl.html#Fl.handle"><TT>handle()</TT></A> method. It then
-becomes the <A
-href="Fl.html#Fl.belowmouse"><TT>Fl::belowmouse()</TT></A>
-widget and will receive <TT>FL_MOVE</TT> and <TT>FL_LEAVE</TT>
+returning non-zero from its
+<A href="Fl.html#Fl.handle"><tt>handle()</tt></A>
+method. It then becomes the
+<A href="Fl.html#Fl.belowmouse"><tt>Fl::belowmouse()</tt></A>
+widget and will receive <tt>FL_MOVE</tt> and <tt>FL_LEAVE</tt>
 events.
 
-<H3>FL_LEAVE</H3>
+\subsection events_fl_leave FL_LEAVE
 
-<P>The mouse has moved out of the widget.
+The mouse has moved out of the widget.
 
-<P>In order to receive the <TT>FL_LEAVE</TT> event, the widget must
-return non-zero when handling <TT>FL_ENTER</TT>.</P>
+In order to receive the <tt>FL_LEAVE</tt> event, the widget must
+return non-zero when handling <tt>FL_ENTER</tt>.
 
-<H3>FL_FOCUS</H3>
+\subsection events_fl_focus FL_FOCUS
 
-<P>This indicates an <I>attempt</I> to give a widget the
+This indicates an <I>attempt</I> to give a widget the
 keyboard focus.
 
-<P>If a widget wants the focus, it should change itself to
-display the fact that it has the focus, and return non-zero from
-its <A
-href="Fl_Widget.html#Fl_Widget.handle"><TT>handle()</TT></A>
-method.  It then becomes the <A
-href="Fl.html#Fl.focus"><TT>Fl::focus()</TT></A> widget and gets
-<TT>FL_KEYDOWN</TT>, <TT>FL_KEYUP</TT>, and <TT>FL_UNFOCUS</TT>
+If a widget wants the focus, it should change itself to
+display the fact that it has the focus, and return non-zero from its
+<A href="Fl_Widget.html#Fl_Widget.handle"><tt>handle()</tt></A>
+method.  It then becomes the
+<A href="Fl.html#Fl.focus"><tt>Fl::focus()</tt></A>
+widget and gets
+<tt>FL_KEYDOWN</tt>, <tt>FL_KEYUP</tt>, and <tt>FL_UNFOCUS</tt>
 events.
 
-<P>The focus will change either because the window manager
+The focus will change either because the window manager
 changed which window gets the focus, or because the user tried
-to navigate using tab, arrows, or other keys. You can check <A
-href="Fl.html#Fl.event_key"><TT>Fl::event_key()</TT></A> to
-figure out why it moved. For navigation it will be the key
-pressed and interaction with the window manager it will be
-zero.
+to navigate using tab, arrows, or other keys. You can check
+<A href="Fl.html#Fl.event_key"><tt>Fl::event_key()</tt></A>
+to figure out why it moved. For navigation it will be the key
+pressed and interaction with the window manager it will be zero.
 
-<H3>FL_UNFOCUS</H3>
+\subsection events_fl_unfocus FL_UNFOCUS
 
-<P>This event is sent to the previous <A
-href="Fl.html#Fl.focus"><TT>Fl::focus()</TT></A> widget when
-another widget gets the focus or the window loses focus.
+This event is sent to the previous
+<A href="Fl.html#Fl.focus"><tt>Fl::focus()</tt></A>
+widget when another widget gets the focus or the window loses focus.
 
-<H2>Keyboard Events</H2>
+\section events_keyboard Keyboard Events
 
-<H3>FL_KEYDOWN, FL_KEYUP</H3>
+\subsection events_fl_keydown FL_KEYDOWN, FL_KEYUP
 
-<P>A key was pressed or released. The key can be found in <A
-href="Fl.html#Fl.event_key"><TT>Fl::event_key()</TT></A>. The
-text that the key should insert can be found with <A
-href="Fl.html#Fl.event_text"><TT>Fl::event_text()</TT></A> and
-its length is in <A
-href="Fl.html#Fl.event_length"><TT>Fl::event_length()</TT></A>. 
-If you use the key <TT>handle()</TT> should return 1. If you
+A key was pressed or released. The key can be found in
+<A href="Fl.html#Fl.event_key"><tt>Fl::event_key()</tt></A>.
+The text that the key should insert can be found with
+<A href="Fl.html#Fl.event_text"><tt>Fl::event_text()</tt></A>
+and its length is in
+<A href="Fl.html#Fl.event_length"><tt>Fl::event_length()</tt></A>. 
+If you use the key <tt>handle()</tt> should return 1. If you
 return zero then FLTK assumes you ignored the key and will
 then attempt to send it to a parent widget. If none of them want
-it, it will change the event into a <TT>FL_SHORTCUT</TT> event.
+it, it will change the event into a <tt>FL_SHORTCUT</tt> event.
 
-<P>To receive <CODE>FL_KEYBOARD</CODE> events you must also
+To receive <CODE>FL_KEYBOARD</CODE> events you must also
 respond to the <CODE>FL_FOCUS</CODE> and <CODE>FL_UNFOCUS</CODE>
 events.
 
-<P>If you are writing a text-editing widget you may also want to
-call the <a href="Fl.html#Fl.compose"><TT>Fl::compose()</TT></a>
-function to translate individual keystrokes into foreign
-characters.
+If you are writing a text-editing widget you may also want to
+call the
+<a href="Fl.html#Fl.compose"><tt>Fl::compose()</tt></a>
+function to translate individual keystrokes into foreign characters.
 
-<P><code>FL_KEYUP</code> events are sent to the widget that 
+<code>FL_KEYUP</code> events are sent to the widget that 
 currently has focus. This is not necessarily the same widget
 that received the corresponding <code>FL_KEYDOWN</code> event
 because focus may have changed between events.
 
-<H3>FL_SHORTCUT</H3>
+\subsection events_fl_shortcut FL_SHORTCUT
 
-<P>If the <A href="Fl.html#Fl.focus"><TT>Fl::focus()</TT></A>
-widget is zero or ignores an <TT>FL_KEYBOARD</TT> event then
+If the
+<A href="Fl.html#Fl.focus"><tt>Fl::focus()</tt></A>
+widget is zero or ignores an <tt>FL_KEYBOARD</tt> event then
 FLTK tries sending this event to every widget it can, until one
-of them returns non-zero. <TT>FL_SHORTCUT</TT> is first sent to
-the <TT>Fl::belowmouse()</TT> widget, then its parents and
+of them returns non-zero. <tt>FL_SHORTCUT</tt> is first sent to
+the <tt>Fl::belowmouse()</tt> widget, then its parents and
 siblings, and eventually to every widget in the window, trying
 to find an object that returns non-zero. FLTK tries really hard
 to not to ignore any keystrokes!
 
-<P>You can also make &quot;global&quot; shortcuts by using <A
-href="Fl.html#Fl.add_handler"><TT>Fl::add_handler()</TT></A>. A
-global shortcut will work no matter what windows are displayed
-or which one has the focus.</P>
+You can also make &quot;global&quot; shortcuts by using
+<A href="Fl.html#Fl.add_handler"><tt>Fl::add_handler()</tt></A>.
+A global shortcut will work no matter what windows are displayed
+or which one has the focus.
 
-<H2>Widget Events</H2>
+\section events_widget Widget Events
 
-<H3>FL_DEACTIVATE</H3>
+\subsection events_fl_deactivate FL_DEACTIVATE
 
-<P>This widget is no longer active, due to <A
-href="Fl_Widget.html#Fl_Widget.deactivate"><TT>deactivate()</TT></A>
-being called on it or one of its parents. <TT> active()</TT> may
+This widget is no longer active, due to
+<A href="Fl_Widget.html#Fl_Widget.deactivate"><tt>deactivate()</tt></A>
+being called on it or one of its parents. <tt> active()</tt> may
 still be true after this, the widget is only active if
-<TT>active()</TT> is true on it and all its parents (use <TT>active_r()</TT> to check this).
+<tt>active()</tt> is true on it and all its parents (use <tt>active_r()</tt> to check this).
 
-<H3>FL_ACTIVATE</H3>
+\subsection events_fl_activate FL_ACTIVATE
 
-<P>This widget is now active, due to <A
-href="Fl_Widget.html#Fl_Widget.activate"><TT>activate()</TT></A>
+This widget is now active, due to
+<A href="Fl_Widget.html#Fl_Widget.activate"><tt>activate()</tt></A>
 being called on it or one of its parents.
 
-<H3>FL_HIDE</H3>
+\subsection events_fl_hide FL_HIDE
 
-<P>This widget is no longer visible, due to <A
-href="Fl_Widget.html#Fl_Widget.hide"><tt>hide()</tt></a> being
-called on it or one of its parents, or due to a parent window
+This widget is no longer visible, due to
+<A href="Fl_Widget.html#Fl_Widget.hide"><tt>hide()</tt></a>
+being called on it or one of its parents, or due to a parent window
 being minimized.  <tt>visible()</tt> may still be true after
 this, but the widget is visible only if <tt>visible()</tt> is
 true for it and all its parents (use <tt>visible_r()</tt> to
 check this).
 
-<h3>FL_SHOW</h3>
+\subsection events_fl_show FL_SHOW
 
-<P>This widget is visible again, due to <a
-href="Fl_Widget.html#Fl_Widget.show"><TT>show()</TT></A> being
-called on it or one of its parents, or due to a parent window
-being restored. <I>Child <TT>Fl_Window</TT>s respond to this by
+This widget is visible again, due to
+<a href="Fl_Widget.html#Fl_Widget.show"><tt>show()</tt></A>
+being called on it or one of its parents, or due to a parent window
+being restored. <I>Child <tt>Fl_Window</tt>s respond to this by
 actually creating the window if not done already, so if you
-subclass a window, be sure to pass <TT>FL_SHOW</TT> to the base
-class <TT>handle()</TT> method!</I>
+subclass a window, be sure to pass <tt>FL_SHOW</tt> to the base
+class <tt>handle()</tt> method!</I>
 
-<H2>Clipboard Events</H2>
+\section events_clipboard Clipboard Events
 
-<H3>FL_PASTE</H3>
+\subsection events_fl_paste FL_PASTE
 
-<P>You should get this event some time after you call <A
-href="Fl.html#Fl.paste"><TT>Fl::paste()</TT></A>. The contents
-of <A href="Fl.html#Fl.event_text"><TT>Fl::event_text()</TT></A>
-is the text to insert and the number of characters is in <A
-href="Fl.html#Fl.event_length"><TT>Fl::event_length()</TT></A>.
+You should get this event some time after you call
+<A href="Fl.html#Fl.paste"><tt>Fl::paste()</tt></A>.
+The contents of
+<A href="Fl.html#Fl.event_text"><tt>Fl::event_text()</tt></A>
+is the text to insert and the number of characters is in
+<A href="Fl.html#Fl.event_length"><tt>Fl::event_length()</tt></A>.
 
-<H3>FL_SELECTIONCLEAR</H3>
+\subsection events_fl_selectionclear FL_SELECTIONCLEAR
 
-<P>The <A
-href="Fl.html#Fl.selection_owner"><TT>Fl::selection_owner()</TT></A>
+The <A href="Fl.html#Fl.selection_owner"><tt>Fl::selection_owner()</tt></A>
 will get this event before the selection is moved to another
 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>
+<A NAME="dnd"></A> <!-- For old HTML links only ! -->
+\section events_dnd Drag and Drop Events
 
-<P>FLTK supports drag and drop of text and files from any 
+FLTK supports drag and drop of text and files from any 
 application on the desktop. Text is transfered using
 the current code page. Files are received as a list of full path
 and file names, seperated by newline. On some platforms, path
 names are prepended with <tt>file://</tt>.
 
-<P>The drag and drop data is available in <tt>Fl::event_text()</tt> 
+The drag and drop data is available in <tt>Fl::event_text()</tt> 
 at the concluding <tt>FL_PASTE</tt>. On some platforms, the
 event text is also available for the <tt>FL_DND_*</tt> events,
 however application must not depend on that behavior because it
 depends on the protocol used on each platform.
 
-<P><tt>FL_DND_*</tt> events cannot be used in widgets derived
+<tt>FL_DND_*</tt> events cannot be used in widgets derived
 from <tt>Fl_Group</tt> or <tt>Fl_Window</tt>.
 
-<H3>FL_DND_ENTER</H3>
+\subsection events_fl_dnd_enter FL_DND_ENTER
 
-<P>The mouse has been moved to point at this widget. A widget
+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>
+\subsection events_fl_dnd_drag FL_DND_DRAG
 
-<P>The mouse has been moved inside a widget while dragging data.
+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>
+\subsection events_fl_dnd_leave FL_DND_LEAVE
 
-<P>The mouse has moved out of the widget.
+The mouse has moved out of the widget.
 
-<H3>FL_DND_RELEASE</H3>
+\subsection events_fl_dnd_release FL_DND_RELEASE
 
-<P>The user has released the mouse button dropping data into 
+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.
 
@@ -273,119 +277,108 @@ the immediatly following FL_PASTE event.
 <A NAME="event_xxx"></A> <!-- For old HTML links only ! -->
 \section events_event_xxx Fl::event_*() methods
 
-<P>FLTK keeps the information about the most recent event in
+FLTK keeps the information about the most recent event in
 static storage. This information is good until the next event is
-processed. Thus it is valid inside <TT>handle()</TT> and
-<TT>callback()</TT> methods.
-
-<P>These are all trivial inline functions and thus very fast and small: </P>
+processed. Thus it is valid inside <tt>handle()</tt> and
+<tt>callback()</tt> methods.
 
-<UL>
+These are all trivial inline functions and thus very fast and small: 
 
-	<LI><A HREF="Fl.html#Fl.event_button"><TT>Fl::event_button</TT></A></LI>
+\li <A HREF="Fl.html#Fl.event_button"><tt>Fl::event_button</tt></A>
 
-	<LI><A HREF="Fl.html#Fl.event_clicks"><TT>Fl::event_clicks</TT></A></LI>
+\li <A HREF="Fl.html#Fl.event_clicks"><tt>Fl::event_clicks</tt></A>
 
-	<LI><A HREF="Fl.html#Fl.event_dx"><TT>Fl::event_dx</TT></A></LI>
+\li <A HREF="Fl.html#Fl.event_dx"><tt>Fl::event_dx</tt></A>
 
-	<LI><A HREF="Fl.html#Fl.event_dy"><TT>Fl::event_dy</TT></A></LI>
+\li <A HREF="Fl.html#Fl.event_dy"><tt>Fl::event_dy</tt></A>
 
-	<LI><A HREF="Fl.html#Fl.event_inside"><TT>Fl::event_inside</TT></A></LI>
+\li <A HREF="Fl.html#Fl.event_inside"><tt>Fl::event_inside</tt></A>
 
-	<LI><A HREF="Fl.html#Fl.event_is_click"><TT>Fl::event_is_click</TT></A></LI>
+\li <A HREF="Fl.html#Fl.event_is_click"><tt>Fl::event_is_click</tt></A>
 
-	<LI><A HREF="Fl.html#Fl.event_key"><TT>Fl::event_key</TT></A></LI>
+\li <A HREF="Fl.html#Fl.event_key"><tt>Fl::event_key</tt></A>
 
-	<LI><A HREF="Fl.html#Fl.event_length"><TT>Fl::event_length</TT></A></LI>
+\li <A HREF="Fl.html#Fl.event_length"><tt>Fl::event_length</tt></A>
 
-	<LI><A HREF="Fl.html#Fl.event_state"><TT>Fl::event_state</TT></A></LI>
+\li <A HREF="Fl.html#Fl.event_state"><tt>Fl::event_state</tt></A>
 
-	<LI><A HREF="Fl.html#Fl.event_text"><TT>Fl::event_text</TT></A></LI>
+\li <A HREF="Fl.html#Fl.event_text"><tt>Fl::event_text</tt></A>
 
-	<LI><A HREF="Fl.html#Fl.event_x"><TT>Fl::event_x</TT></A></LI>
+\li <A HREF="Fl.html#Fl.event_x"><tt>Fl::event_x</tt></A>
 
-	<LI><A HREF="Fl.html#Fl.event_x_root"><TT>Fl::event_x_root</TT></A></LI>
+\li <A HREF="Fl.html#Fl.event_x_root"><tt>Fl::event_x_root</tt></A>
 
-	<LI><A HREF="Fl.html#Fl.event_y"><TT>Fl::event_y</TT></A></LI>
+\li <A HREF="Fl.html#Fl.event_y"><tt>Fl::event_y</tt></A>
 
-	<LI><A HREF="Fl.html#Fl.event_y_root"><TT>Fl::event_y_root</TT></A></LI>
+\li <A HREF="Fl.html#Fl.event_y_root"><tt>Fl::event_y_root</tt></A>
 
-	<LI><A HREF="Fl.html#Fl.get_key"><TT>Fl::get_key</TT></A></LI>
+\li <A HREF="Fl.html#Fl.get_key"><tt>Fl::get_key</tt></A>
 
-	<LI><A HREF="Fl.html#Fl.get_mouse"><TT>Fl::get_mouse</TT></A></LI>
+\li <A HREF="Fl.html#Fl.get_mouse"><tt>Fl::get_mouse</tt></A>
 
-	<LI><A HREF="Fl.html#Fl.test_shortcut"><TT>Fl::test_shortcut</TT></A></LI>
-
-</UL>
+\li <A HREF="Fl.html#Fl.test_shortcut"><tt>Fl::test_shortcut</tt></A>
 
 <A NAME="event_xxx"></A> <!-- For old HTML links only ! -->
 \section events_propagation Event Propagation
 
-<P>FLTK follows very simple and unchangeable rules for sending
+FLTK follows very simple and unchangeable rules for sending
 events. The major innovation is that widgets can indicate (by
-returning 0 from the <TT>handle()</TT> method) that they are not
+returning 0 from the <tt>handle()</tt> method) that they are not
 interested in an event, and FLTK can then send that event
 elsewhere.  This eliminates the need for &quot;interests&quot;
 (event masks or tables), and this is probably the main reason
 FLTK is much smaller than other toolkits.
 
-<P>Most events are sent directly to the <TT>handle()</TT> method
-of the <TT>Fl_Window</TT> that the window system says they
-belong to.  The window (actually the <TT>Fl_Group</TT> that
-<TT>Fl_Window</TT> is a subclass of) is responsible for sending
+Most events are sent directly to the <tt>handle()</tt> method
+of the <tt>Fl_Window</tt> that the window system says they
+belong to.  The window (actually the <tt>Fl_Group</tt> that
+<tt>Fl_Window</tt> is a subclass of) is responsible for sending
 the events on to any child widgets.  To make the
-<TT>Fl_Group</TT> code somewhat easier, FLTK sends some events
-(<TT>FL_DRAG</TT>, <TT>FL_RELEASE</TT>, <TT>FL_KEYBOARD</TT>,
-<TT>FL_SHORTCUT</TT>, <TT>FL_UNFOCUS</TT>, and
-<TT>FL_LEAVE</TT>) directly to leaf widgets. These procedures
+<tt>Fl_Group</tt> code somewhat easier, FLTK sends some events
+(<tt>FL_DRAG</tt>, <tt>FL_RELEASE</tt>, <tt>FL_KEYBOARD</tt>,
+<tt>FL_SHORTCUT</tt>, <tt>FL_UNFOCUS</tt>, and
+<tt>FL_LEAVE</tt>) directly to leaf widgets. These procedures
 control those leaf widgets:
 
-<UL>
-
-	<LI><A HREF="Fl.html#Fl.add_handler"><TT>Fl::add_handler</TT></A></LI>
+\li <A HREF="Fl.html#Fl.add_handler"><tt>Fl::add_handler</tt></A>
 
-	<LI><A HREF="Fl.html#Fl.belowmouse"><TT>Fl::belowmouse</TT></A></LI>
+\li <A HREF="Fl.html#Fl.belowmouse"><tt>Fl::belowmouse</tt></A>
 
-	<LI><A HREF="Fl.html#Fl.focus"><TT>Fl::focus</TT></A></LI>
+\li <A HREF="Fl.html#Fl.focus"><tt>Fl::focus</tt></A>
 
-	<LI><A HREF="Fl.html#Fl.grab"><TT>Fl::grab</TT></A></LI>
+\li <A HREF="Fl.html#Fl.grab"><tt>Fl::grab</tt></A>
 
-	<LI><A HREF="Fl.html#Fl.modal"><TT>Fl::modal</TT></A></LI>
+\li <A HREF="Fl.html#Fl.modal"><tt>Fl::modal</tt></A>
 
-	<LI><A HREF="Fl.html#Fl.pushed"><TT>Fl::pushed</TT></A></LI>
+\li <A HREF="Fl.html#Fl.pushed"><tt>Fl::pushed</tt></A>
 
-	<LI><A HREF="Fl.html#Fl.release"><TT>Fl::release</TT></A></LI>
+\li <A HREF="Fl.html#Fl.release"><tt>Fl::release</tt></A>
 
-	<LI><A HREF="Fl_Widget.html#Fl_Widget.take_focus"><TT>Fl_Widget::take_focus</TT></A></LI>
+\li <A HREF="Fl_Widget.html#Fl_Widget.take_focus"><tt>Fl_Widget::take_focus</tt></A>
 
-</UL>
+<A name="compose"></A> <!-- For old HTML links only ! -->
+\section events_compose_characters FLTK Compose-Character Sequences
 
-<H2><A name="compose">FLTK Compose-Character Sequences</A></H2>
+The foreign-letter compose processing done by the
+<A href="Fl_Input.html#compose"><tt>Fl_Input</tt></a>
+widget is provided in a function that you can call if you are writing
+your own text editor widget.
 
-<P>The foreign-letter compose processing done by the <A
-href="Fl_Input.html#compose"><tt>Fl_Input</tt></a> widget is provided in
-a function that you can call if you are writing your own text editor
-widget.
-
-<p>FLTK uses its own compose processing to allow "preview" of
+FLTK uses its own compose processing to allow "preview" of
 the partially composed sequence, which is impossible with the
 usual "dead key" processing.
 
-<p>Although currently only characters in the ISO-8859-1
+Although currently only characters in the ISO-8859-1
 character set are handled, you should call this in case any
 enhancements to the processing are done in the future. The
 interface has been designed to handle arbitrary UTF-8 encoded
 text.
 
-<P>The following methods are provided for character composition:
-
-<UL>
-
-	<LI><A HREF="Fl.html#Fl.compose"><TT>Fl::compose()</TT></A></LI>
+The following methods are provided for character composition:
 
-	<LI><A HREF="Fl.html#Fl.compose_reset"><TT>Fl::compose_reset()</TT></A></LI>
+\li <A HREF="Fl.html#Fl.compose"><tt>Fl::compose()</tt></A>
 
-</UL>
+\li <A HREF="Fl.html#Fl.compose_reset"><tt>Fl::compose_reset()</tt></A>
 
 <hr>
 <a class="el" href="index.html">[Index]</a> &nbsp;&nbsp;