More image updates, minor typos, etc.

git-svn-id: file:///fltk/svn/fltk/trunk@227 ea41ed52-d2ee-0310-a9c1-e6b18d33e121

documentation/Fl_Gl_Window.html

@@ -127,8 +127,7 @@ context for this window or when the window resizes, and is turned on <I>
 after</I><TT>draw()</TT> is called.  You can use this inside your <TT>
 draw()</TT> method to avoid unneccessarily initializing the OpenGL 
 context.  Just do this: 
-<UL>
-<PRE>
+<UL><PRE>
 void mywindow::draw() {
   if (!valid()) {
     glViewport(0,0,w(),h());
@@ -138,9 +137,7 @@ void mywindow::draw() {
   }
   ... draw your geometry here ...
 }
-
-<BR>void Fl_Gl_Window::invalidate();
-<BR>void Fl_Gl_Window::valid(char i);
+</PRE></UL>
 
 <TT>Fl_Gl_Window::valid()</TT> is turned off when FLTK creates a
 new context for this window and by the window resizing, and is turned
@@ -148,8 +145,8 @@ on <I>after</I> draw() is called.  You can use this inside your draw()
 method to avoid unneccessarily initializing the OpenGL context.  Just
 do this:
 
-</PRE>
-<PRE><TT>void mywindow::draw() {
+<UL><PRE>
+void mywindow::draw() {
   if (!valid()) {
     glViewport(0,0,w(),h());
     glFrustum(...);
@@ -158,11 +155,11 @@ do this:
   }
   ... draw your geometry here ...
 }
-</TT></PRE>
-</UL>
- You can turn <TT>valid()</TT> on by calling <TT>valid(1)</TT>.  You 
+</PRE></UL>
+
+You can turn <TT>valid()</TT> on by calling <TT>valid(1)</TT>.  You 
 should only do this after fixing the transformation inside a <TT>draw()</TT>
- or after <TT>make_current()</TT>.  This is done automatically after <TT>
+or after <TT>make_current()</TT>.  This is done automatically after <TT>
 draw()</TT> returns. 
 <H4><A name=Fl_Gl_Window.invalidate>void Fl_Gl_Window::invalidate()</A></H4>
  The <TT>invalidate()</TT> method turns off <TT>valid()</TT> and is 
@@ -215,4 +212,4 @@ Fl_Gl_Window::valid()</TT> and set the same transformation.  If you
 don't your code may not work on other systems.  Depending on the OS, 
 and on whether overlays are real or simulated, the OpenGL context may 
 be the same or different between the overlay and main window. </P>
-</BODY></HTML>
+</BODY></HTML>

documentation/Fl_Group.html

@@ -87,9 +87,7 @@ automatically called by the constructor for Fl_Group (and thus for
 Fl_Window as well). <TT>begin()</TT> does <TT>current(this)</TT>. 
 <P><I>Don't forget to <TT>end()</TT> the group or window!</I></P>
 <H4><A name=Fl_Group.child>Fl_Widget *Fl_Group::child(int n) const</A></H4>
- Returns child <TT>n</TT>, where <TT>0 
-<!--= n < children()</tt-->
-. 
+ Returns child <TT>n</TT>, where <TT>0 &lt;= n &lt; children()</TT>. 
 <H4><A name=Fl_Group.children>int Fl_Group::children() const</A></H4>
  Returns how many child widgets the group has. 
 <H4><A name=Fl_Group.current>static Fl_Group *Fl_Group::current()
@@ -133,4 +131,4 @@ and distance from the top-left corner. </P>
 <P>It is possible to achieve any type of resize behavior by using an 
 invisible <TT>Fl_Box</TT> as the resizable and/or by using a hierarchy 
 of child <TT>Fl_Group</TT>'s. </P>
-</TT></BODY></HTML>
+</TT></BODY></HTML>

documentation/Fl_Input.html

@@ -27,8 +27,8 @@ will correctly display anything, using ^X notation for unprintable
 control characters and \nnn notation for unprintable characters with 
 the high bit set. It assummes the font can draw any characters in the 
 ISO8859-1 character set. 
-<TABLE border=1>
-<TR><TD><B>Mouse button 1</B></TD><TD>Moves the cursor to this point. 
+<CENTER><TABLE border=1 WIDTH=90%>
+<TR><TD WIDTH=200><B>Mouse button 1</B></TD><TD>Moves the cursor to this point. 
  Drag selects characters.  Double click selects words.  Triple click 
 selects all text.  Shift+click extends the selection.</TD></TR>
 <TR><TD><B>Mouse button 2</B></TD><TD>Insert the current X selection at 
@@ -71,7 +71,7 @@ into a single &quot;undo&quot;.  Often this will undo a lot more than you
 expected.</TD></TR>
 <TR><TD><B>Shift+move</B></TD><TD>Move the cursor but also extend the 
 selection.</TD></TR>
-</TABLE>
+</TABLE></CENTER>
 <H3>Methods</H3>
 <CENTER>
 <TABLE width=90%>
@@ -176,4 +176,4 @@ fields. </LI>
 <H4><A name=Fl_Input.cursor_color>Fl_Color Fl_Input::cursor_color() 
 const
 <BR> void Fl_Input::cursor_color(Fl_Color)</A></H4>
- Get or set the color of the cursor.  This is black by default. </BODY></HTML>
+ Get or set the color of the cursor.  This is black by default. </BODY></HTML>

documentation/Fl_Menu_.html

@@ -96,9 +96,9 @@ focus when you type it.  This is done by using <A href=osissues.html#add_handler
 <TT>Fl::add_handler()</TT></A>.  This <TT>Fl_Menu_</TT> widget does not 
 have to be visible (ie the window it is in can be hidden, or it does 
 not have to be put in a window at all). 
-<P>Currently there can be only one <TT>global()<TT>menu.  Setting a new 
+<P>Currently there can be only one <TT>global()</TT>menu.  Setting a new 
 one will replace the old one.  There is no way to remove the <TT>
-global()</TT> setting (including destroying the menu). </TT></TT></P>
+global()</TT> setting (including destroying the menu). </TT></P>
 <H4><A name=Fl_Menu_.text>const char* Fl_Menu_::text() const
 <BR> const char* Fl_Menu_::text(int i) const</A></H4>
  Returns the title of the last item chosen, or of item <TT>i</TT>. 
@@ -160,4 +160,4 @@ Fl_Menu_</TT> widget if it uses it's own array.
  This box type is used to surround the currently-selected items in the 
 menus.  If this is <TT>FL_NO_BOX</TT> then it acts like <TT>
 FL_THIN_UP_BOX</TT> and <TT>selection_color()</TT> acts like <TT>
-FL_WHITE</TT>, for back compatability. </BODY></HTML>
+FL_WHITE</TT>, for back compatability. </BODY></HTML>

documentation/Fl_Menu_Bar.html

@@ -27,7 +27,7 @@ single <A href=Fl_Menu_Item.html#Fl_Menu_Item><TT>Fl_Menu_Item</TT></A>
 top level menu defines the items in the menubar, while the submenus 
 define the pull-down menus. Sub-sub menus and lower pop up to the right 
 of the submenus. </P>
-<P><IMG src=./menubar.gif></P>
+<P ALIGN=CENTER><IMG src=menubar.gif></P>
 <P>If there is an item in the top menu that is not a title of a 
 submenu, then it acts like a &quot;button&quot; in the menubar.  Clicking on it 
 will pick it. </P>
@@ -60,4 +60,4 @@ put it outside the menubar. </P>
 <H4><A name=Fl_Menu_Bar.~Fl_Menu_Bar>virtual Fl_Menu_Bar::~Fl_Menu_Bar()</A>
 </H4>
  The destructor removes the <TT>Fl_Menu_Bar</TT> widget and all of its 
-menu items. </BODY></HTML>
+menu items. </BODY></HTML>

documentation/Fl_Menu_Button.html

@@ -20,7 +20,7 @@
  This is a button that when pushed pops up a menu (or hierarchy of 
 menus) defined by an array of <A href=Fl_Menu_Item.html#Fl_Menu_Item><TT>
 Fl_Menu_Item</TT></A> objects. 
-<P><IMG src=./menu_button.gif></P>
+<P ALIGN=CENTER><IMG src=menu_button.gif></P>
 <P>Normally any mouse button will pop up a menu and it is lined up 
 below the button as shown in the picture.  However an <TT>Fl_Menu_Button</TT>
  may also control a pop-up menu.  This is done by setting the <TT>type()</TT>
@@ -59,8 +59,8 @@ its menu items.
 shortcut key.  The menu appears, it waits for the user to pick an item, 
 and if they pick one it sets <TT>value()</TT> and does the callback or 
 sets <TT>changed()</TT> as described above.  The menu item is returned 
-or <TT>NULL<TT>if the user dismisses the menu. 
-<H4><A name=Fl_Menu_Button.type>void Fl_Widget::type(uchar)</A></H4>
+or <TT>NULL</TT>if the user dismisses the menu. 
+<H4><A name=Fl_Menu_Button.type>void Fl_Menu_Button::type(uchar)</A></H4>
  If <TT>type()</TT> is zero a normal menu button is produced.  If it is 
 nonzero then this is a pop-up menu.  The bits in <TT>type()</TT>
  indicate what mouse buttons pop up the menu.  For convienece the 
@@ -76,4 +76,4 @@ widgets covering different areas for context-sensitive popup menus. </P>
 selected item.  This is a <I>feature</I>.  If you don't like it, do <TT>
 value(0)</TT> after the menu items are picked to forget the current 
 item. </P>
-</TT></TT></BODY></HTML>
+</BODY></HTML>

documentation/Fl_Positioner.html

@@ -21,7 +21,7 @@
 It would be useful if this could be put atop another widget so that the 
 crosshairs are on top, but this is not implemented.  The color of the 
 crosshairs is <TT>selection_color()</TT>. 
-<P><IMG src=./positioner.gif></P>
+<P ALIGN=CENTER><IMG src=positioner.gif></P>
 <H3>Methods</H3>
 <CENTER>
 <TABLE width=90%>
@@ -66,4 +66,4 @@ float *y) const</A></H4>
  Sets the stepping value for the Y axis. 
 <H4><A name=Fl_Positioner.yvalue>float Fl_Positioner::yvalue(void) const
 <BR> void Fl_Positioner::yvalue(float y)</A></H4>
- Gets or sets the Y axis coordinate. </BODY></HTML>
+ Gets or sets the Y axis coordinate. </BODY></HTML>

documentation/Fl_Scroll.html

@@ -21,7 +21,7 @@
 larger than your window.  If the child widgets are larger than the size 
 of this object then scrollbars will appear so that you can scroll over 
 to them: 
-<P><IMG src=./Fl_Scroll.gif></P>
+<P ALIGN=CENTER><IMG src=Fl_Scroll.gif></P>
 <P>If all of the child widgets are packed together into a solid 
 rectangle then you want to set <TT>box()</TT> to <TT>FL_NO_BOX</TT> or 
 one of the <TT>_FRAME</TT> types. This will result in the best output. 
@@ -96,4 +96,4 @@ the top.
  Gets the current vertical scrolling position. 
 <H4><A name=Fl_Scroll.position>void Fl_Scroll::position(int w, int h)</A>
 </H4>
- Sets the upper-lefthand corner of the scrolling region. </BODY></HTML>
+ Sets the upper-lefthand corner of the scrolling region. </BODY></HTML>

documentation/Fl_Single_Window.html

@@ -17,7 +17,7 @@
 </PRE>
 </UL>
 <H3>Description</H3>
- This is the same as <TT>Fl_Window<TT>.  However, it is possible that 
+ This is the same as <TT>Fl_Window</TT>.  However, it is possible that 
 some implementations will provide double-buffered windows by default. 
 This subclass can be used to force single-buffering.  This may be 
 useful for modifying existing programs that use incremental update, or 
@@ -34,4 +34,5 @@ char *label = 0)</A></H4>
 position, size, and label (title) string. 
 <H4><A name=Fl_Single_Window.~Fl_Single_Window>virtual 
 Fl_Single_Window::~Fl_Single_Window()</A></H4>
- Destroys the window and all child widgets. </TT></TT></BODY></HTML>
+ Destroys the window and all child widgets.
+</BODY></HTML>

documentation/Fl_Tabs.html

@@ -20,7 +20,7 @@
  The <TT>Fl_Tabs</TT> widget is the &quot;file card tabs&quot; interface that 
 allows you to put lots and lots of buttons and switches in a panel, as 
 popularized by many toolkits. 
-<P><IMG src=./tabs.gif></P>
+<P ALIGN=CENTER><IMG src=tabs.gif></P>
 <P>Clicking the tab makes a child <TT>visible()</TT> (by calling <TT>
 show()</TT> on it) and all other children are invisible (by calling <TT>
 hide()</TT> on them).  Usually the children are <A href=Fl_Group.html#Fl_Group>
@@ -61,4 +61,4 @@ variables, but you must declare the <TT>Fl_Tab</TT><I>first</I>, so
 that it is destroyed last. 
 <H4><A name=Fl_Tab.value>Fl_Widget* Fl_Tabs::value() const
 <BR> int Fl_Tabs::value(Fl_Widget*)</A></H4>
- Gets or sets the currently visible widget/tab. </BODY></HTML>
+ Gets or sets the currently visible widget/tab. </BODY></HTML>

documentation/Fl_Tile.html

@@ -21,7 +21,7 @@
 <H3>Description</H3>
  The <TT>Fl_Tile</TT> class lets you resize the children by dragging 
 the border between them: 
-<P><IMG src=./Fl_Tile.gif></P>
+<P ALIGN=CENTER><IMG src=Fl_Tile.gif></P>
 <P><TT>Fl_Tile</TT> allows objects to be resized to zero dimensions. 
  To prevent this you can use the <TT>resizable()</TT> to limit where 
 corners can be dragged to. </P>
@@ -30,10 +30,10 @@ initially have non-zero sizes so the <TT>Fl_Tile</TT> can figure out
 their layout.  If desired, call <TT>position()</TT> after creating the 
 children but before displaying the window to set the borders where you 
 want. </P>
-<P>The &quot;borders&quot; are part of the children, an <TT>Fl_Tile<TT>does not 
+<P>The &quot;borders&quot; are part of the children, an <TT>Fl_Tile</TT>does not 
 draw any graphics of it's own.  In the above example all the final 
 children have <TT>FL_DOWN_BOX</TT> types, and the &quot;ridges&quot; you see are 
-two adjacent <TT>FL_DOWN_BOX</TT>'s drawn next to each other. </TT></TT></P>
+two adjacent <TT>FL_DOWN_BOX</TT>'s drawn next to each other. </P>
 <H3>Methods</H3>
 <UL>
 <LI><A href=#Fl_Tile.Fl_Tile>Fl_Tile</A></LI>
@@ -56,10 +56,11 @@ that it is destroyed last.
 to_x, to_y)</A></H4>
  Drag the intersection at <TT>from_x,from_y</TT> to <TT>to_x,to_y</TT>. 
  This redraws all the necessary children. 
-<H4><A name=Fl_Tile.resizeable>void Fl_Tile::resizable(Fl_Widget The 
-&quot;resizable&quot; child widget (which should be invisible) limits where the 
+<H4><A name=Fl_Tile.resizeable>void Fl_Tile::resizable(Fl_Widget &amp;w)<BR>
+void Fl_Tile::resizable(Fl_Widget *w)</A></H4>
+The &quot;resizable&quot; child widget (which should be invisible) limits where the 
 border can be dragged to.  If you don't set it, it will be possible to 
 drag the borders right to the edge, and thus resize objects on the edge 
 to zero width or height.  The <TT>resizable()</TT> widget is not 
-resized by dragging any borders. </A></H4>
-</BODY></HTML>
+resized by dragging any borders.
+</BODY></HTML>

documentation/Fl_Valuator.html

@@ -24,13 +24,13 @@
 and provides a consistent interface to set the value, range, and step, 
 and insures that callbacks are done the same for every object. 
 <P>There are probably more of these classes in fltk than any others: </P>
-<P><IMG src=./valuators.gif></P>
+<P ALIGN=CENTER><IMG src=valuators.gif WIDTH=60%></P>
 <P>In the above diagram each box surrounds an actual subclass.  These 
 are further differentiated by setting the <A href=#Fl_Widget.type"><TT>
 type()</TT></A> of the widget to the symbolic value labeling the 
 widget.  The ones labelled &quot;0&quot; are the default versions with a <TT>
-type(0)<TT>.  For consistency the symbol <TT>FL_VERTICAL</TT> is 
-defined as zero. </TT></TT></P>
+type(0)</TT>.  For consistency the symbol <TT>FL_VERTICAL</TT> is 
+defined as zero.</P>
 <H3>Methods</H3>
 <CENTER>
 <TABLE width=90%>
@@ -133,4 +133,4 @@ turn it back on if desired).
 <H4>Sets the <TT>changed()</TT> flag. </H4>
 <H4><A name=Fl_Valuator.clear_changed>void Fl_Widget::clear_changed()</A>
 </H4>
- Clears the <TT>changed()</TT> flag. </BODY></HTML>
+ Clears the <TT>changed()</TT> flag. </BODY></HTML>

documentation/Fl_Value_Slider.html

@@ -19,7 +19,7 @@
 <H3>Description</H3>
  The <TT>Fl_Value_Slider</TT> widget is a <TT>Fl_Slider</TT> widget 
 with a box displaying the current value. 
-<P><IMG src=./value_slider.gif></P>
+<P ALIGN=CENTER><IMG src=value_slider.gif></P>
 <H3>Methods</H3>
 <UL>
 <LI><A href=#Fl_Value_Slider.Fl_Value_Slider>Fl_Value_Slider</A></LI>
@@ -49,4 +49,4 @@ Fl_Value_Slider::textfont() const
 <H4><A name=Fl_Value_Slider.textsize>uchar Fl_Value_Slider::textsize() 
 const
 <BR> void Fl_Value_Slider::textsize(uchar)</A></H4>
- Gets or sets the size of the text in the value box. </BODY></HTML>
+ Gets or sets the size of the text in the value box. </BODY></HTML>

documentation/Fl_Widget.html

@@ -167,18 +167,17 @@ the label as text.
 <BR> void Fl_Widget::align(Fl_Align)</A></H4>
  How the label is printed next to or inside the widget.  The default 
 value is <TT>FL_ALIGN_CENTER</TT>, which centers the label.  The value 
-can be any of these constants or'd together: <TT>
+can be any of these constants or'd together:
 <UL>
-<LI>FL_ALIGN_CENTER </LI>
-<LI>FL_ALIGN_TOP </LI>
-<LI>FL_ALIGN_BOTTOM </LI>
-<LI>FL_ALIGN_LEFT </LI>
-<LI>FL_ALIGN_RIGHT </LI>
-<LI>FL_ALIGN_INSIDE </LI>
-<LI>FL_ALIGN_CLIP </LI>
-<LI>FL_ALIGN_WRAP </LI>
+<LI><TT>FL_ALIGN_CENTER</TT></LI>
+<LI><TT>FL_ALIGN_TOP</TT></LI>
+<LI><TT>FL_ALIGN_BOTTOM</TT></LI>
+<LI><TT>FL_ALIGN_LEFT</TT></LI>
+<LI><TT>FL_ALIGN_RIGHT</TT></LI>
+<LI><TT>FL_ALIGN_INSIDE</TT></LI>
+<LI><TT>FL_ALIGN_CLIP</TT></LI>
+<LI><TT>FL_ALIGN_WRAP</TT></LI>
 </UL>
-</TT>
 <H4><A name=Fl_Widget.labelcolor>Fl_Color Fl_Widget::labelcolor() const
 <BR> void Fl_Widget::labelcolor(Fl_Color)</A></H4>
  This color is passed to the labeltype routine, and is typically the 

documentation/Makefile

@@ -1,5 +1,5 @@
 #
-# "$Id: Makefile,v 1.5 1999/01/13 16:25:15 mike Exp $"
+# "$Id: Makefile,v 1.6 1999/01/14 22:14:00 mike Exp $"
 #
 # Documentation makefile for the Fast Light Tool Kit (FLTK).
 #
@@ -115,7 +115,7 @@ HTMLFILES	= \
 		osissues.html \
 		license.html
 
-all:	fltk.ps fltk.pdf
+all:	fltk.ps fltk.pdf fltk.d/index.html
 
 clean:
 	rm -rf fltk.d
@@ -130,7 +130,7 @@ fltk.d/index.html: $(HTMLFILES)
 	@echo "Generating HTML documentation..."
 	@-mkdir fltk.d
 	@-rm -f fltk.d/*
-	@$(HTMLDOC) -d fltk.d -t html --verbose --toclevels 2 --title FL.gif $(HTMLFILES)
+	@$(HTMLDOC) -d fltk.d -t html --verbose --toclevels 2 --bodycolor white --title FL.gif $(HTMLFILES)
 
 fltk.ps: $(HTMLFILES)
 	@echo "Generating PostScript documentation..."
@@ -142,5 +142,5 @@ fltk.pdf: $(HTMLFILES)
 	@$(HTMLDOC) -f fltk.pdf --compression=9 --jpeg=90 --duplex --verbose --toclevels 2 --title FL.gif $(HTMLFILES)
 
 #
-# End of "$Id: Makefile,v 1.5 1999/01/13 16:25:15 mike Exp $".
+# End of "$Id: Makefile,v 1.6 1999/01/14 22:14:00 mike Exp $".
 #

documentation/forms.html

@@ -166,7 +166,7 @@ have to rewrite things a lot. </P>
 <H3>You Cannot Use &lt;device.h&gt;</H3>
  If you have written your own &quot;free&quot; widgets you will probably get a 
 lot of errors about &quot;getvaluator&quot;.  You should substitute: 
-<TABLE border=1>
+<CENTER><TABLE border=1 WIDTH=90%>
 <TR><TH align=center>Forms</TH><TH align=center>FLTK</TH></TR>
 <TR><TD>MOUSE_X</TD><TD>Fl::event_x_root()</TD></TR>
 <TR><TD>MOUSE_Y</TD><TD>Fl::event_y_root()</TD></TR>
@@ -177,7 +177,7 @@ lot of errors about &quot;getvaluator&quot;.  You should substitute:
 <TR><TD>MOUSE1,RIGHTMOUSE</TD><TD>Fl::event_state()</TD></TR>
 <TR><TD>MOUSE2,MIDDLEMOUSE</TD><TD>Fl::event_state()</TD></TR>
 <TR><TD>MOUSE3,LEFTMOUSE</TD><TD>Fl::event_state()</TD></TR>
-</TABLE>
+</TABLE></CENTER>
  Anything else in <TT>getvaluator</TT> and you are on your own... 
 <H3>Font Numbers Are Different</H3>
  The &quot;style&quot; numbers have been changed because I wanted to insert 

documentation/functions.html

@@ -559,11 +559,9 @@ other programs).  The window <I>does not have to be <TT>shown()</TT></I>
 all event handling and allows you to map and unmap a complex set of 
 windows (under both X and WIN32 <I>some</I> window must be mapped 
 because the system interface needs a window id). 
-<P><TT>Fl::event_x()</TT> and <TT>Fl::event_y()
-<!--.tt-->
- are undefined if the 
+<P><TT>Fl::event_x()</TT> and <TT>Fl::event_y()</TT> are undefined if the 
 passed widget is not a mapped <TT>Fl_Window</TT>.  Use <TT>
-Fl::event_x_root()</TT> and <TT>Fl::event_y_root()</TT> instead. </TT></P>
+Fl::event_x_root()</TT> and <TT>Fl::event_y_root()</TT> instead.</P>
 <P><I>Be careful that your program does not enter an infinite loop 
 while <TT>grab()</TT> is on.  On X this will lock up your screen!</I></P>
 <P>The second function returns the current grab window, or <TT>NULL</TT>