This repository was archived by the owner on Aug 31, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 223
Expand file tree
/
Copy pathmainStackChanged.xml
More file actions
45 lines (45 loc) · 2.28 KB
/
Copy pathmainStackChanged.xml
File metadata and controls
45 lines (45 loc) · 2.28 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
<doc>
<legacy_id>1278</legacy_id>
<name>mainStackChanged</name>
<type>message</type>
<syntax>
<example>mainStackChanged</example>
</syntax>
<library></library>
<objects>
<stack/>
</objects>
<synonyms>
</synonyms>
<classification>
<category>Objects & Messages</category>
</classification>
<references>
<property tag="mainStack">mainStack Property</property>
</references>
<history>
<introduced version="1.0">Added.</introduced>
</history>
<platforms>
<mac/>
<windows/>
<linux/>
<ios/>
<android/>
</platforms>
<classes>
<desktop/>
<server/>
<web/>
<mobile/>
</classes>
<security>
</security>
<summary>Sent to a <object tag="stack">stack</object> when its <property tag="mainStack">mainStack</property> is changed.</summary>
<examples>
<example>on mainStackChanged <code><i>-- in a main stack's script</i></code></p><p> save me <code><i>-- save the stack file when a substack is added</i></code></p><p>end mainStackChanged</example>
</examples>
<description>
<p>Handle the <b>mainStackChanged</b> <keyword tag="message box">message</keyword> if you want to respond when a <glossary tag="substack">substack</glossary> is moved to another <glossary tag="stack file">stack file</glossary>.</p><p/><p><b>Comments:</b></p><p>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 <b>mainStack</b> property to the name of the main stack of the destination file. The moved stack becomes a substack of the main stack you specified.</p><p/><p>The <b>mainStackChanged</b> 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 <b>mainStackChanged</b> message is received by the new main stack, and can be handled in the main stack's script.</p><p/><p>The <b>mainStackChanged</b> <keyword tag="message box">message</keyword> is used by the LiveCode <glossary tag="development environment">development environment</glossary>, so if you <glossary tag="handle">handle</glossary> this <keyword tag="message box">message</keyword>, be sure to <control_st tag="pass">pass</control_st> it at the end of the <glossary tag="handler">handler</glossary>.</p>
</description>
</doc>