summaryrefslogtreecommitdiff
path: root/documentation
diff options
context:
space:
mode:
authorMatthias Melcher <fltk@matthiasm.com>2006-11-26 13:48:04 +0000
committerMatthias Melcher <fltk@matthiasm.com>2006-11-26 13:48:04 +0000
commitf49f038cdbf6236e9ef398711dfc046200c4241b (patch)
tree3efd5cd5f6fd5bb49f0c3ed54a4346f92ca97eba /documentation
parent67f87f028531d487f730b823e1325dab0cd827bf (diff)
Updated the Fl_Tile documentation, hoping that the way it works becomes a bit clearer. I would like to ask a native English speaker to look over my text though. Thanks.
git-svn-id: file:///fltk/svn/fltk/branches/branch-1.1@5551 ea41ed52-d2ee-0310-a9c1-e6b18d33e121
Diffstat (limited to 'documentation')
-rw-r--r--documentation/Fl_Tile.html29
1 files changed, 18 insertions, 11 deletions
diff --git a/documentation/Fl_Tile.html b/documentation/Fl_Tile.html
index 35a01e52c..8918cc2f0 100644
--- a/documentation/Fl_Tile.html
+++ b/documentation/Fl_Tile.html
@@ -31,6 +31,24 @@ the border between them:
<P ALIGN=CENTER><IMG src="Fl_Tile.gif" ALT="Fl_Tile widget."></P>
+<P>For the tiling to work correctly, the children of an
+<TT>Fl_Tile</TT> must cover the entire area of the widget, but not
+overlap. This means that all children must touch each
+other at their edges, and no gaps can't be left inside the
+<TT>Fl_Tile</TT>.
+
+<P><TT>Fl_Tile</TT> does not normailly draw any graphics of its own.
+The &quot;borders&quot; which can be seen in the snapshot above
+are actually part of the children. Their boxtypes have been set
+to <TT>FL_DOWN_BOX</TT> creating the impression of
+&quot;ridges&quot; where the boxes touch. What you see are
+actually two adjacent <TT>FL_DOWN_BOX</TT>'s drawn next to each
+other. All neighboring widgets share the same edge - the widget's
+thick borders make it appear as though the widgets aren't actually
+touching, but they are. If the edges of adjacent widgets do not
+touch, then it will be impossible to drag the corresponding
+edges.</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>
@@ -41,17 +59,6 @@ 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 -
-<TT>Fl_Tile</TT> does not draw any graphics of its own. In the
-example above, all of the children have <TT>FL_DOWN_BOX</TT>
-types, and the &quot;ridges&quot; you see are actually two
-adjacent <TT>FL_DOWN_BOX</TT>'s drawn next to each other. All
-neighboring widgets share the same edge - the widget's thick
-borders make it appear as though the widgets aren't actually
-touching, but they are. If the edges of adjacent widgets do not
-touch, then it will be impossible to drag the corresponding
-edges.</P>
-
<H3>Methods</H3>
<UL>
<LI><A href=#Fl_Tile.Fl_Tile>Fl_Tile</A></LI>