Skip to content

Commit fc43c3f

Browse files
author
livecodesam
authored
Correct code example and clarify about close/open messages
Corrected text to clarify that all close*/(pre)open* messages are sent during standalone building. Corrected code example to not fail when a user working on a stack using that code finishes working on the stack without having saved it as a standalone.
1 parent daa380b commit fc43c3f

File tree

1 file changed

+10
-8
lines changed

1 file changed

+10
-8
lines changed

docs/notes-base/breaking_changes.md

Lines changed: 10 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -11,18 +11,20 @@ few problems, for example:
1111

1212
As an attempt to improve this situation, the code that locks messages
1313
when closing and opening stacks for standalone builds has been removed.
14-
This means that where previously mainstacks would not receive openStack
15-
and closeStack messages during standalone build, they now do.
14+
This means that where previously mainstacks would not receive any of the
15+
`(pre)open*` and `close*` messages (e.g. `preOpenStack`, `openStack`,
16+
`openCard`, `closeStack` etc) during standalone build, they now do.
1617

1718
If this causes problems for your stack, you can exit from the handler if
1819
standalone building is in progress:
1920

20-
on closeStack
21-
if the environment is "development" and \
22-
the mode of stack "revStandaloneProgress" > 0 then
23-
exit closeStack
24-
end if
25-
end closeStack
21+
on closeStack
22+
if the environment is "development" and \
23+
there is a stack "revStandaloneProgress" and \
24+
the mode of stack "revStandaloneProgress" > 0 then
25+
exit closeStack
26+
end if
27+
end closeStack
2628

2729
## LiveCode Builder
2830

0 commit comments

Comments
 (0)