diff --git a/documentation/Fl_Text_Buffer.html b/documentation/Fl_Text_Buffer.html index ebc4a913b..a7629e26b 100644 --- a/documentation/Fl_Text_Buffer.html +++ b/documentation/Fl_Text_Buffer.html @@ -31,80 +31,88 @@ excellent NEdit text editor engine - see
|
|
|
|
|
After including the required header files, the program then creates a window:
@@ -114,11 +116,12 @@ of the form "type name() const".Almost all of the set/get pairs are very fast, short inline -functions and thus very efficient. However, the "set" -methods do not call redraw() - you have to call it -yourself. This greatly reduces code size and execution time. -The only common exception is value() which calls -redraw() if necessary.
+functions and thus very efficient. However, the "set" methods +do not call redraw() - you have to call it +yourself. This greatly reduces code size and execution time. The +only common exceptions are value() which calls +redraw() and label() which calls +redraw_label() if necessary.The forms, GL, and images libraries are included with the "--use-foo" +options, as follows: + +
+CC ... `fltk-config --use-forms --ldflags` +CC ... `fltk-config --use-gl --ldflags` +CC ... `fltk-config --use-images --ldflags` +CC ... `fltk-config --use-forms --use-gl --use-images --ldflags` ++
Finally, you can use the fltk-config script to compile a single source file as a FLTK program:
fltk-config --compile filename.cpp +fltk-config --use-forms --compile filename.cpp +fltk-config --use-gl --compile filename.cpp +fltk-config --use-images --compile filename.cpp +fltk-config --use-forms --use-gl --use-images --compile filename.cpp-
This will create an executable named filename. +
Any of these will create an executable named filename.
The proper way to include FLTK header files is:
@@ -296,16 +317,24 @@ better and can be used with the "optimized for speed" setting. #include <FL/Fl_xyz.H> -Microsoft Windows developers please note: case *is* -significant under other operating systems, and the C standard -uses the forward slash (/) to separate directories. Do not -use any of the following include lines:
+Note:
--#include <FL\Fl_xyz.H> -#include <fl/fl_xyz.h> -#include <Fl/fl_xyz.h> -+ Case is significant on many operating systems, + and the C standard uses the forward slash (/) to + separate directories. Do not use any of the following + include lines: + ++ #include <FL\Fl_xyz.H> + #include <fl/fl_xyz.h> + #include <Fl/fl_xyz.h> ++ + |
+