Fixed a few typos.

git-svn-id: file:///fltk/svn/fltk/branches/branch-1.3@6837 ea41ed52-d2ee-0310-a9c1-e6b18d33e121
This commit is contained in:
Albrecht Schlosser 2009-07-29 16:29:26 +00:00
parent 4fb3b8c80d
commit 7e8ba419c6
2 changed files with 5 additions and 7 deletions

View File

@ -274,7 +274,7 @@ An example:
void MyWindow::show() {
if (shown()) {Fl_Window::show(); return;} // you must do this!
fl_open_display(); // necessary if this is first window
// we only calcualte the necessary visual colormap once:
// we only calculate the necessary visual colormap once:
static XVisualInfo *visual;
static Colormap colormap;
if (!visual) {

View File

@ -14,11 +14,10 @@ typically Fl_Widget for controls and Fl_Group for composite widgets.
A control widget typically interacts with the user to receive and/or
display a value of some sort.
A composite widget widget holds a list of child widgets and handles moving,
sizing, showing, or hiding them as needed. Fl_Group is the
main composite widget widget class in FLTK, and all of the other composite
widgets (Fl_Pack, Fl_Scroll, Fl_Tabs,
Fl_Tile, and Fl_Window) are subclasses of it.
A composite widget holds a list of child widgets and handles moving,
sizing, showing, or hiding them as needed. Fl_Group is the main
composite widget class in FLTK, and all of the other composite widgets
(Fl_Pack, Fl_Scroll, Fl_Tabs, Fl_Tile, and Fl_Window) are subclasses of it.
You can also subclass other existing widgets to provide a different
look or user-interface. For example, the button widgets are all
@ -518,7 +517,6 @@ differences:
-# Fl_Window is a subclass of Fl_Group so
<I>make sure your constructor calls</I> \p end()
unless you actually want children added to your window.
-# When handling events and drawing, the upper-left corner is at
0,0, not <tt>x(),y()</tt> as in other Fl_Widget's.
For instance, to draw a box around the widget, call