From a6163888f3c56123b1db313743c6147ba498732c Mon Sep 17 00:00:00 2001 From: Yuval Adam Date: Fri, 8 Aug 2014 14:42:07 +0300 Subject: Add third_party libs --- .../windows/fltk-1.1.10/documentation/Fl_Tile.html | 91 ++++++++++++++++++++++ 1 file changed, 91 insertions(+) create mode 100644 third_party/windows/fltk-1.1.10/documentation/Fl_Tile.html (limited to 'third_party/windows/fltk-1.1.10/documentation/Fl_Tile.html') diff --git a/third_party/windows/fltk-1.1.10/documentation/Fl_Tile.html b/third_party/windows/fltk-1.1.10/documentation/Fl_Tile.html new file mode 100644 index 0000000..73df45f --- /dev/null +++ b/third_party/windows/fltk-1.1.10/documentation/Fl_Tile.html @@ -0,0 +1,91 @@ + + + Fl_Tile + + + + + +

class Fl_Tile

+ +
+ +

Class Hierarchy

+ + + +

Include Files

+ + + +

Description

+ +

The Fl_Tile class lets you resize the children by dragging +the border between them: + +

Fl_Tile widget.

+ +

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.

+ +

Even though objects can be resized to zero sizes, they must +initially have non-zero sizes so the Fl_Tile can figure out +their layout. If desired, call position() after creating the +children but before displaying the window to set the borders where you +want.

+ +

Methods

+ +

Fl_Tile::Fl_Tile(int x, int y, int w, int +h, const char *label = 0)

+ Creates a new Fl_Tile widget using the given position, size, +and label string. The default boxtype is FL_NO_BOX. +

virtual Fl_Tile::~Fl_Tile()

+ The destructor also deletes all the children. 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 +Fl_Tile and all of it's children can be automatic (local) +variables, but you must declare the Fl_Tile first, so +that it is destroyed last. +

void Fl_Tile::position(from_x, from_y, +to_x, to_y)

+ Drag the intersection at from_x,from_y to to_x,to_y. + This redraws all the necessary children. +

void Fl_Tile::resizable(Fl_Widget &w)
+void Fl_Tile::resizable(Fl_Widget *w)

+The "resizable" 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 resizable() widget is not +resized by dragging any borders. + -- cgit v1.3.1