forked from livecode/livecode
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathkeyUp.lcdoc
More file actions
53 lines (37 loc) · 1.48 KB
/
keyUp.lcdoc
File metadata and controls
53 lines (37 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
50
51
52
Name: keyUp
Type: message
Syntax: keyUp <pKeyName>
Summary:
Sent when the user releases a pressed key.
Associations: card,field
Introduced: 1.0
OS: mac, windows, linux, ios, android
Platforms: desktop, server, mobile
Example:
on keyUp -- play a keyclick sound
-- in this example, the parameter is not needed or used
play audioClip "click"
end keyUp
Parameters:
pKeyName:
The actual character of the pressed key.
Description:
Handle the <keyUp> <message> if you want to do something special when
the user releases any key (or a particular key you check for in the
<handler>).
The message is sent to the active (focused) control, or to the current
card if no control is focused.
If the key pressed is the Return, Tab, Backspace, Delete, or Enter key,
an arrow key, or a function key, no <keyUp> <message> is sent.
>*Cross-platform note:* On <Mac OS|Mac OS systems>, the <keyUp>
> <message> is sent after any <keyDown> <handler|handlers> finish
> <execute|executing>, whether or not the key has been released. On
> <Unix> and <Windows|Windows systems>, the <keyUp> <message> is sent
> when the key is released, after the typed character has been added to
> the current <field>. To test whether a key is actually being pressed,
> use the <keysDown> <function>.
References: focus (command), function (control structure),
keysDown (function), handler (glossary), Unix (glossary),
message (glossary), Windows (glossary), Mac OS (glossary),
execute (glossary), field (keyword), keyDown (message)
Tags: ui