forked from livecode/livecode
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathmainStackChanged.lcdoc
More file actions
33 lines (19 loc) · 1.4 KB
/
Copy pathmainStackChanged.lcdoc
File metadata and controls
33 lines (19 loc) · 1.4 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
Name: mainStackChanged
Type: message
Syntax: mainStackChanged
Summary: Sent to a <stack> when its <mainStack> is changed.
Associations: stack
Introduced: 1.0
OS: mac,windows,linux,ios,android
Platforms: desktop,server,web,mobile
Example:
on mainStackChanged -- in a main stack's script
save me -- save the stack file when a substack is added
end mainStackChanged
Description:
Handle the <mainStackChanged> <message> if you want to respond when a <substack> is moved to another <stack file>.
Each stack file consists of a main stack, and may also include one or more substacks. To move a stack to another file, you set its <mainStack> property to the name of the main stack of the destination file. The moved stack becomes a substack of the main stack you specified.
The <mainStackChanged> message is sent right after the stack is moved to the new stack file. This means that (if the substack does not trap the message) the <mainStackChanged> message is received by the new main stack, and can be handled in the main stack's script.
The <mainStackChanged> <message> is used by the LiveCode <development environment>, so if you <handle> this <message>, be sure to <pass> it at the end of the <handler>.
References: mainStack (property), stack (object), substack (glossary), stack file (glossary), message (glossary), handler (glossary), handle (glossary), development environment (glossary), pass (control_st)
Tags: objects