Documentation updates galore (up to chapter 7, still need to do chapter

8 and 9, tweek the appendices, and recapture the screenshots...)


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

1 files changed, 26 insertions, 26 deletions

diff --git a/documentation/Fl_Tile.html b/documentation/Fl_Tile.html
index cd2afc2b5..977326308 100644
--- a/documentation/Fl_Tile.html
+++ b/documentation/Fl_Tile.html
@@ -17,21 +17,21 @@
 </PRE>
 </UL>
 <H3>Description</H3>
- The <TT>Fl_Tile</TT> class lets you resize the children by dragging 
-the border between them: 
+ The <TT>Fl_Tile</TT> class lets you resize the children by dragging
+the border between them:
 <P ALIGN=CENTER><IMG src="Fl_Tile.gif" ALT="Fl_Tile widget."></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 
+<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>
-<P>Even though objects can be resized to zero sizes, they must 
-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 
+<P>Even though objects can be resized to zero sizes, they must
+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 
-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 
+ <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. </P>
 <H3>Methods</H3>
 <UL>
@@ -40,26 +40,26 @@ two adjacent <TT>FL_DOWN_BOX</TT>'s drawn next to each other. </P>
 <LI><A href=#Fl_Tile.position>position</A></LI>
 <LI><A href=#Fl_Tile.resizeable>resizeable</A></LI>
 </UL>
-<H4><A name=Fl_Tile.Fl_Tile>Fl_Tile::Fl_Tile(int x, int y, int w, int 
+<H4><A name=Fl_Tile.Fl_Tile>Fl_Tile::Fl_Tile(int x, int y, int w, int
 h, const char *label = 0)</A></H4>
- Creates a new <TT>Fl_Tile</TT> widget using the given position, size, 
-and label string. The default boxtype is <TT>FL_NO_BOX</TT>. 
+ Creates a new <TT>Fl_Tile</TT> widget using the given position, size,
+and label string. The default boxtype is <TT>FL_NO_BOX</TT>.
 <H4><A name=Fl_Tile.~Fl_Tile>virtual Fl_Tile::~Fl_Tile()</A></H4>
- The destructor <I>also deletes all the children</I>. This allows a 
-whole tree to be deleted at once, without having to keep a pointer to 
+ The destructor <I>also deletes all the children</I>. This allows a
+whole tree to be deleted at once, without having to keep a pointer to
 all the children in the user code. A kludge has been done so the <TT>
-Fl_Tile</TT> and all of it's children can be automatic (local) 
-variables, but you must declare the <TT>Fl_Tile</TT> <I>first</I>, so 
-that it is destroyed last. 
-<H4><A name=Fl_Tile.position>void Fl_Tile::position(from_x, from_y, 
+Fl_Tile</TT> and all of it's children can be automatic (local)
+variables, but you must declare the <TT>Fl_Tile</TT> <I>first</I>, so
+that it is destroyed last.
+<H4><A name=Fl_Tile.position>void Fl_Tile::position(from_x, from_y,
 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. 
+ 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 &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 
+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.
 </BODY></HTML>