forked from livecode/livecode
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathallowInlineInput.lcdoc
More file actions
50 lines (35 loc) · 1.48 KB
/
Copy pathallowInlineInput.lcdoc
File metadata and controls
50 lines (35 loc) · 1.48 KB
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
Name: allowInlineInput
Type: property
Syntax: set the allowInlineInput to {true | false}
Summary:
Specifies whether the user can type non-Roman text directly into a
<field>.
Introduced: 2.0
OS: mac, windows
Platforms: desktop, server
Example:
set the allowInlineInput to true
Example:
set the allowInlineInput to the letUsersType of this stack
Value (bool):
The allowInput property is true or false.
By default, the <allowInlineInput> is true.
Description:
Use the <allowInlineInput> <property> to determine the method by which
the user can enter <double-byte character|double-byte> text.
If the <allowInlineInput> <property> is set to true, the user can type
<double-byte character|double-byte characters> (used for languages that
do not use the Roman alphabet, such as Chinese, Japanese, and Korean)
directly into <field(object)|fields>.
If the <allowInlineInput> is false, if the <insertion point> is in a
<field(keyword)> and a double-byte language is currently selected, a
text-entry <palette> appears where the user can enter the <characters>.
(This palette is displayed by the operating system's language software,
not by LiveCode.) When the user presses Enter, the <characters> are
placed in the <field(keyword)>.
References: palette (command), property (glossary),
insertion point (glossary), double-byte character (glossary),
field (keyword), characters (keyword), field (object),
traversalOn (property), textFont (property), lockText (property),
useUnicode (property)
Tags: text processing