Fixed typos in documentation, inspired by the list of typos found by

Josef Vitu in FLTK 1.3. Thanks again.


git-svn-id: file:///fltk/svn/fltk/branches/branch-1.1@6947 ea41ed52-d2ee-0310-a9c1-e6b18d33e121
This commit is contained in:
Albrecht Schlosser 2009-11-29 16:40:09 +00:00
parent 8ee53e3538
commit 3344eaffca
9 changed files with 16 additions and 16 deletions

View File

@ -79,7 +79,7 @@ A submenu title is identified by the bit <TT>FL_SUBMENU</TT> in the <TT>
flags</TT> field, and ends with a <TT>label()</TT> that is <TT>NULL</TT>.
You can nest menus to any depth. A pointer to the first item in the
submenu can be treated as an <TT>Fl_Menu</TT> array itself. It is also
possible to make seperate submenu arrays with <TT>FL_SUBMENU_POINTER</TT>
possible to make separate submenu arrays with <TT>FL_SUBMENU_POINTER</TT>
flags.
<P>You should use the method functions to access structure members and
not access them directly to avoid compatibility problems with future

View File

@ -45,7 +45,7 @@ yet exist.
<P>Entries can be of any length. However, the size of each
preferences file should be kept under 100k for performance
reasons. One application can have multiple preferences files.
Extensive binary data however should be stored in seperate
Extensive binary data however should be stored in separate
files; see the <A
href="#Fl_Preferences.getUserdataPath"><tt>getUserdataPath()</tt></A>
method.

View File

@ -363,9 +363,9 @@ a filled, neutral box (<TT>UP_BOX</TT>), a filled, depressed box
and <TT>DOWN_FRAME</TT>). The function
<TT><A HREF="#fl_down">fl_down(Fl_Boxtype)</A></TT>
expects the neutral design on a boxtype with a numerical
value evenly divideable by two.
value evenly dividable by two.
<TT><A HREF="#fl_frame">fl_frame(Fl_Boxtype)</A></TT>
expects the <TT>UP_BOX</TT> design at a value divideable by four.</P>
expects the <TT>UP_BOX</TT> design at a value dividable by four.</P>
<H2><A NAME="labels">Labels and Label Types</A></H2>
@ -396,7 +396,7 @@ sign. Figure 3-4 shows the available symbols.</P>
<LI>+[1-9] or -[1-9] tweaks the scaling a little bigger
or smaller.</LI>
<LI>'$' flips the symbol horizontaly, '%' flips it verticaly.</LI>
<LI>'$' flips the symbol horizontally, '%' flips it vertically.</LI>
<LI>[0-9] - rotates by a multiple of 45 degrees. '5' and
'6' do no rotation while the others point in the
@ -480,7 +480,7 @@ method sets the image that is shown when the widget is active.</P>
<P>Label types are actually indexes into a table of functions
that draw them. The primary purpose of this is to use this to
draw the labels in ways inaccessible through the
<TT>fl_font</TT> mechanisim (e.g. <TT>FL_ENGRAVED_LABEL</TT>) or
<TT>fl_font</TT> mechanism (e.g. <TT>FL_ENGRAVED_LABEL</TT>) or
with program-generated letters or symbology.</P>
<CENTER><TABLE WIDTH="80%" BORDER="1" CELLPADDING="5" CELLSPACING="0" BGCOLOR="#cccccc">

View File

@ -437,7 +437,7 @@ angle is in degrees (not radians) and is counter-clockwise.
<P>Transform a coordinate or a distance trough the current transformation matrix.
After transforming a coordinate pair, it can be added to the vertex
list without any forther translations using <tt>fl_transformed_vertex</tt>.
list without any further translations using <tt>fl_transformed_vertex</tt>.
<H4><A NAME=fl_begin_points>void fl_begin_points()
<BR>void fl_end_points()</A></H4>
@ -466,7 +466,7 @@ the list with <tt>fl_vertex</tt>.
<P>Start and end drawing a complex filled polygon. This polygon
may be concave, may have holes in it, or may be several
disconnected pieces. Call <TT>fl_gap()</TT> to seperate loops of
disconnected pieces. Call <TT>fl_gap()</TT> to separate loops of
the path. It is unnecessary but harmless to call
<TT>fl_gap()</TT> before the first vertex, after the last one,
or several times in a row.

View File

@ -239,7 +239,7 @@ selection indication. Most modern programs ignore this.
<P>FLTK supports drag and drop of text and files from any
application on the desktop. Text is transfered using
the current code page. Files are received as a list of full path
and file names, seperated by newline. On some platforms, path
and file names, separated by newline. On some platforms, path
names are prepended with <tt>file://</tt>.
<P>The drag and drop data is available in <tt>Fl::event_text()</tt>
@ -271,7 +271,7 @@ indicate the possible drop position.
<P>The user has released the mouse button dropping data into
the widget. If the widget returns 1, it will receive the data in
the immediatly following FL_PASTE event.
the immediately following FL_PASTE event.
<!-- NEED 6in -->

View File

@ -166,7 +166,7 @@ the use of timeouts and matrix based drawing.
<tt>colbrowser</tt> runs only on X11 systems. It reads
<i>/usr/lib/X11/rgb.txt</i> to show the color representation
of every text entry in the file. This is beautiful, but
only moderatly useful unless your UI is written in <i>Motif</i>.
only moderately useful unless your UI is written in <i>Motif</i>.
<h3><a name="color_chooser">color_chooser</h3>
The <tt>color_chooser</tt> gives a short demo of FLTK's palette based
@ -376,7 +376,7 @@ button behavior.
<h3><a name="resizebox">resizebox</h3>
<tt>resizebox</tt> shows some possible ways of FLTK's automatic
resize bahavior..
resize behavior.
<h3><a name="resize">resize</h3>
The <tt>resize</tt> demo tests size and position functions with

View File

@ -766,7 +766,7 @@ Widgets will be sorted from first to last.
<H4>Layout/Make Same Size/... </H4>
<P>Make all slected widgets the same size as the first selected widget.
<P>Make all selected widgets the same size as the first selected widget.
<H4>Layout/Center in Group/... </H4>

View File

@ -64,7 +64,7 @@ required so many changes it made it impossible to recompile any
Forms objects. Since it was incompatible anyway, Bill decided
to incorporate his older ideas as much as possible by
simplifying the lower level interface and the event passing
mechanisim.</P>
mechanism.</P>
<P>Bill received permission to release it for free on the
Internet, with the GNU general public license. Response from

View File

@ -162,10 +162,10 @@ identifier, and can be set with the protected method <TT>type(uchar t)</TT>
. This value had to be provided for Forms compatibility, but you can
use it for any purpose you want. Try to keep the value less than 100
to not interfere with reserved values.
<P>FLTK does not use RTTI (Run Time Typing Infomation), to enhance
<P>FLTK does not use RTTI (Run Time Typing Information), to enhance
portability. But this may change in the near future if RTTI becomes
standard everywhere. </P>
<P>If you don't have RTTI you can use the clumsy FLTK mechanisim, by
<P>If you don't have RTTI you can use the clumsy FLTK mechanism, by
having <TT>type()</TT> use a unique value. These unique values must
be greater than the symbol <TT>FL_RESERVED_TYPE</TT> (which is 100).
Look through the header files for <TT>FL_RESERVED_TYPE</TT> to find an