diff options
| author | Michael R Sweet <michael.r.sweet@gmail.com> | 1999-01-13 19:28:54 +0000 |
|---|---|---|
| committer | Michael R Sweet <michael.r.sweet@gmail.com> | 1999-01-13 19:28:54 +0000 |
| commit | d7b88a3bcc7e76f38ee5799be7722fd5a10781ef (patch) | |
| tree | d8984d45424c9b2cdb199c1918f38bfea4a8211d /documentation/Fl_Multiline_Input.html | |
| parent | 30fa233681467b82b165e7d42cd0bea778b93768 (diff) | |
Updated all links so they work between files.
Revision 1.
git-svn-id: file:///fltk/svn/fltk/trunk@219 ea41ed52-d2ee-0310-a9c1-e6b18d33e121
Diffstat (limited to 'documentation/Fl_Multiline_Input.html')
| -rw-r--r-- | documentation/Fl_Multiline_Input.html | 94 |
1 files changed, 42 insertions, 52 deletions
diff --git a/documentation/Fl_Multiline_Input.html b/documentation/Fl_Multiline_Input.html index 1b157eace..278b591a3 100644 --- a/documentation/Fl_Multiline_Input.html +++ b/documentation/Fl_Multiline_Input.html @@ -1,53 +1,43 @@ -<html> -<body> - -<hr break> - -<h2><a name="Fl_Multiline_Input">class Fl_Multiline_Input</a></h2> - -<hr> - -<h3>Class Hierarchy</h3> - -<ul><pre> -<a href="#Fl_Input">Fl_Input</a> +<HTML><BODY> +<HR break> +<H2><A name=Fl_Multiline_Input>class Fl_Multiline_Input</A></H2> +<HR> +<H3>Class Hierarchy</H3> +<UL> +<PRE> +<A href=functions.html#Fl_Input>Fl_Input</A> | - +----<b>Fl_Multiline_Input</b> -</pre></ul> - -<h3>Include Files</h3> - -<ul><pre> -#include <FL/Fl_Input.H> -</pre></ul> - -<h3>Description</h3> - -This input field displays '\n' characters as new lines rather than ^J, -and accepts the Return, Tab, and up and down arrow keys. This is for -editing multiline text. - -<p>This is far from the nirvana of text editors, and is probably only -good for small bits of text, 10 lines at most. I think FLTK can be -used to write a powerful text editor, but it is not going to be a -built-in feature. Powerful text editors in a toolkit are a big source -of bloat. - -<h3>Methods</h3> - -<ul> - <li><a href="#Fl_Multiline_Input.Fl_Multiline_Input">Fl_Multiline_Input</a> - <li><a href="#Fl_Multiline_Input.~Fl_Multiline_Input">~Fl_Multiline_Input</a> -</ul> - -<h4><a name="Fl_Multiline_Input.Fl_Multiline_Input">Fl_Multiline_Input::Fl_Multiline_Input(int x, int y, int w, int h, const char *label = 0)</a></h4> - -Creates a new <tt>Fl_Multiline_Input</tt> widget using the given position, size, and -label string. The default boxtype is <tt>FL_DOWN_BOX</tt>. - -<h4><a name="Fl_Multiline_Input.~Fl_Multiline_Input">virtual Fl_Multiline_Input::~Fl_Multiline_Input()</a></h4> - -Destroys the widget and any value associated with it. - -</body> -</html> + +----<B>Fl_Multiline_Input</B> +</PRE> +</UL> +<H3>Include Files</H3> +<UL> +<PRE> +#include <FL/Fl_Input.H> +</PRE> +</UL> +<H3>Description</H3> + This input field displays '\n' characters as new lines rather than ^J, +and accepts the Return, Tab, and up and down arrow keys. This is for +editing multiline text. +<P>This is far from the nirvana of text editors, and is probably only +good for small bits of text, 10 lines at most. I think FLTK can be +used to write a powerful text editor, but it is not going to be a +built-in feature. Powerful text editors in a toolkit are a big source +of bloat. </P> +<H3>Methods</H3> +<UL> +<LI><A href=#Fl_Multiline_Input.Fl_Multiline_Input>Fl_Multiline_Input</A> +</LI> +<LI><A href=#Fl_Multiline_Input.~Fl_Multiline_Input>~Fl_Multiline_Input</A> +</LI> +</UL> +<H4><A name=Fl_Multiline_Input.Fl_Multiline_Input> +Fl_Multiline_Input::Fl_Multiline_Input(int x, int y, int w, int h, +const char *label = 0)</A></H4> + Creates a new <TT>Fl_Multiline_Input</TT> widget using the given +position, size, and label string. The default boxtype is <TT>FL_DOWN_BOX</TT> +. +<H4><A name=Fl_Multiline_Input.~Fl_Multiline_Input>virtual +Fl_Multiline_Input::~Fl_Multiline_Input()</A></H4> + Destroys the widget and any value associated with it. </BODY></HTML>
\ No newline at end of file |