summaryrefslogtreecommitdiff
path: root/documentation/Fl_Multiline_Input.html
blob: 1b157eace57b5f228c4fe60e507fb77e83a19f01 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
<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 &lt;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>