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:
For the tiling to work correctly, the children of an +Fl_Tile 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 +Fl_Tile. + +
Fl_Tile does not normailly draw any graphics of its own. +The "borders" which can be seen in the snapshot above +are actually part of the children. Their boxtypes have been set +to FL_DOWN_BOX creating the impression of +"ridges" where the boxes touch. What you see are +actually two adjacent FL_DOWN_BOX'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.
+Fl_Tile allows objects to be resized to zero dimensions. To prevent this you can use the resizable() to limit where corners can be dragged to.
@@ -41,17 +59,6 @@ their layout. If desired, call position() after creating the children but before displaying the window to set the borders where you want. -The "borders" are part of the children - -Fl_Tile does not draw any graphics of its own. In the -example above, all of the children have FL_DOWN_BOX -types, and the "ridges" you see are actually two -adjacent FL_DOWN_BOX'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.
-