Correct code example and clarify about close/open messages

livecodesam · web-flow · commit fc43c3fd3478 · 2018-09-20T12:05:02.000+01:00
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.
diff --git a/docs/notes-base/breaking_changes.md b/docs/notes-base/breaking_changes.md
@@ -11,18 +11,20 @@ few problems, for example:
 	
 As an attempt to improve this situation, the code that locks messages
 when closing and opening stacks for standalone builds has been removed.
-This means that where previously mainstacks would not receive openStack
-and closeStack messages during standalone build, they now do.
+This means that where previously mainstacks would not receive any of the 
+`(pre)open*` and `close*` messages (e.g. `preOpenStack`, `openStack`, 
+`openCard`, `closeStack` etc) during standalone build, they now do.
 
 If this causes problems for your stack, you can exit from the handler if 
 standalone building is in progress:
 
-	on closeStack
-		if the environment is "development" and \
-                    the mode of stack "revStandaloneProgress" > 0 then
-			exit closeStack
-		end if
-	end closeStack
+    on closeStack
+        if the environment is "development" and \
+          there is a stack "revStandaloneProgress" and \
+          the mode of stack "revStandaloneProgress" > 0 then
+            exit closeStack
+        end if
+    end closeStack
 
 ## LiveCode Builder
 
