forked from livecode/livecode
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathbackScripts.lcdoc
More file actions
50 lines (34 loc) · 1.44 KB
/
Copy pathbackScripts.lcdoc
File metadata and controls
50 lines (34 loc) · 1.44 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: backScripts
Type: function
Syntax: the backScripts
Syntax: backScripts()
Summary:
<return|Returns> a list of <object|objects> that have been inserted into
the <message path> after the <stack> the target <object(glossary)>
belongs to.
Introduced: 1.0
OS: mac, windows, linux, ios, android
Platforms: desktop, server, mobile
Example:
the backScripts
Example:
if the long ID of me is not among the lines of the backScripts then beep
Returns:
The <backScripts> function returns a list of the long ID property of all
objects that have been inserted into the back, one ID per line.
Description:
Use the <backScripts> function to find out which scripts receive
messages and function calls after the current object, the objects that
own the current object, and any stacks in the stacksInUse.
A script inserted into the back with the <insert script> command
receives messages after all objects in the message path, just before the
application itself receives the message.
If more than one object is in the <backScripts>, their order in the
message path is the same as their order in the list. For example, the
first object in the <backScripts> receives messages before the second
object. This order is the reverse of the order in which the objects were
added with the <insert script> command.
References: remove script (command), insert script (command),
object (glossary), message path (glossary), return (glossary),
back (keyword), stack (object)
Tags: objects