From 87dd7f0d23eba5c09e71ec6efeb34c6844f5e95f Mon Sep 17 00:00:00 2001 From: Michael R Sweet Date: Tue, 29 Dec 1998 14:21:17 +0000 Subject: Revised documentation files. git-svn-id: file:///fltk/svn/fltk/trunk@177 ea41ed52-d2ee-0310-a9c1-e6b18d33e121 --- documentation/Fl_Tabs.html | 85 ++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 85 insertions(+) create mode 100644 documentation/Fl_Tabs.html (limited to 'documentation/Fl_Tabs.html') diff --git a/documentation/Fl_Tabs.html b/documentation/Fl_Tabs.html new file mode 100644 index 000000000..3018aeecd --- /dev/null +++ b/documentation/Fl_Tabs.html @@ -0,0 +1,85 @@ + + + +
+ +

class Fl_Tabs

+ +
+ +

Class Hierarchy

+ + + +

Include Files

+ + + +

Description

+ +The Fl_Tabs widget is the "file card tabs" interface that +allows you to put lots and lots of buttons and switches in a panel, as +popularized by many toolkits. + +

+ +

Clicking the tab makes a child visible() (by calling +show() on it) and all other children are invisible (by calling +hide() on them). Usually the children are Fl_Group widgets containing several +widgets themselves. + +

Each child makes a card, and it's label() is printed on the +card tab (including the label font and style). The color of that child +is used to color the card as well. Currently this only draws nicely if +you set box() to the default +FL_THIN_UP_BOX or to FL_FLAT_BOX, which gets rid of +the edges drawn on the sides and bottom. + +

The size of the tabs is controlled by the bounding box of the +children (there should be some space between the children and the edge +of the Fl_Tabs), and the tabs may be placed "inverted" on the +bottom, this is determined by which gap is larger. It is easiest to +lay this out in fluid, using the fluid browser to select each child +group and resize them until the tabs look the way you want them to. + +

Methods

+ + + +

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

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

Use add(Fl_Widget *) to add +each child (which is probably itself a Fl_Group). The +children should be sized to stay away from the top or bottom edge of +the Fl_Tabs, which is where the tabs are drawn. + +

virtual Fl_Tab::~Fl_Tab()

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

Fl_Widget* Fl_Tabs::value() const
+int Fl_Tabs::value(Fl_Widget*)

+ +Gets or sets the currently visible widget/tab. + + + -- cgit v1.2.3