87dd7f0d23
git-svn-id: file:///fltk/svn/fltk/trunk@177 ea41ed52-d2ee-0310-a9c1-e6b18d33e121
54 lines
1.4 KiB
HTML
54 lines
1.4 KiB
HTML
<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>
|
|
|
|
|
+----<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>
|