diff options
| author | Michael R Sweet <michael.r.sweet@gmail.com> | 1999-01-07 16:36:11 +0000 |
|---|---|---|
| committer | Michael R Sweet <michael.r.sweet@gmail.com> | 1999-01-07 16:36:11 +0000 |
| commit | 367f908d8ed5a3464b9676223a26ddf4e11bdb5b (patch) | |
| tree | 2b0ec583852973ccf7b9804957e78d474e0e7e5d /documentation/basics.html | |
| parent | 85e6f449590eeb6e09f7547733adf4c7137470d0 (diff) | |
"Final" changes for first draft of 1.0 documentation.
git-svn-id: file:///fltk/svn/fltk/trunk@187 ea41ed52-d2ee-0310-a9c1-e6b18d33e121
Diffstat (limited to 'documentation/basics.html')
| -rw-r--r-- | documentation/basics.html | 13 |
1 files changed, 6 insertions, 7 deletions
diff --git a/documentation/basics.html b/documentation/basics.html index 62e74d7e0..d3b01a5b8 100644 --- a/documentation/basics.html +++ b/documentation/basics.html @@ -31,7 +31,7 @@ The proper way to include FLTK header files is: #include <FL/Fl_xyz.H> </pre></ul> -Microsoft Windows developers please note: case *is* significant +<b>Microsoft Windows developers please note:</b> case *is* significant under other operating systems, and the C standard uses the forward slash (/) to separate directories. The following <tt>#include</tt> directives are *not* recommended for portability reasons: @@ -71,9 +71,8 @@ header files. This can be done by selecting "Settings" from the <p>You can build your Microsoft Windows applications as Console or WIN32 applications. If you want to use the standard C <tt>main()</tt> -function as the entry point, enter the name <tt>mainCRTStartup</tt> in -the "Entry-point symbol" field in the "Output" settings under the -"Link" tab. +function as the entry point, FLTK includes a <tt>WinMain()</tt> function +that will call your <tt>main()</tt> function for you. <p><i>Note: The Visual C++ optimizer is known to cause problems with many programs. We only recommend using the "Favor Small Code" @@ -155,7 +154,7 @@ The <tt>boxtype</tt> value is the style of the box that is drawn around the widget. Usually this is <tt>FL_NO_BOX</tt>, which means that no box is drawn. In our "Hello, World!" example we use <tt>FL_UP_BOX</tt>, which means that a raised button border will be drawn around the -widget. You can learn more about boxtypes in <a href="#common">Chapter +widget. You can learn more about boxtypes in <a href="#boytypes">Chapter 3</a>. <p>The <tt>x</tt> and <tt>y</tt> parameters determine where the widget @@ -170,7 +169,7 @@ governed by the underlying window system or hardware. <H3>Labels</H3> All widgets support labels. In the case of window widgets, the label -is used for the label in the title bar. Our example program calls the +is used for the label in the title bar. Our example program calls the <a href="#Fl_Widget.labelfont"><tt>labelfont</tt></a>, <a href="#Fl_Widget.labelsize"><tt>labelsize</tt></a>, and <a href="#Fl_Widget.labeltype"><tt>labeltype</tt></a> methods. @@ -185,7 +184,7 @@ directly. <p>The <tt>labeltype</tt> method sets the type of label. FLTK supports normal, embossed, shadowed, symbol, and image labels. -<p>A complete list of all label options can be found in <a href="#common"> +<p>A complete list of all label options can be found in <a href="#labels"> Chapter 3</a>. <H3>Showing the Window</H3> |