I think the problem is in the splash stack, which is where the blocking
handlers should go. When LC builds a standalone, it clones the one in the
IDE and creates the standalone from that. Then it reopens the original
which now triggers all the handlers in the original. You don't really need
to worry about the other stacks, just the one that triggers the opening of
the working stack(s). When the SB finishes, it will reopen the splash and
the blocks will prevent any other stacks from loading into memory. That
may mean you need to use the message box to trigger the handler that opens
the others right after the SB finishes.
The problem may be that LC doesn't close its own copy properly before
reopening the original. I'd submit a bug report and include your stack(s)
so they can take a look. Ideally there would be an option or property that
would let us decide whether messages should be locked or not. It would be
nice if the engine could store variable values, create the standalone with
messages locked, and then restore the values after the build.
I'm not sure Curry's suggestion will work, since the SB manages
lockmessages on its own. I've tried scripting a lock messages and it was
ignored.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On May 3, 2024 11:41:24 AM Bob Sneidar via use-livecode
<use-livecode@lists.runrev.com> wrote:
Hi Curry.
I use a Splash Stack which then opens what I call the mainStack. Should I
put this in the closeStack of the splash stack or the main stack?
Bob S
On May 3, 2024, at 8:38 AM, Curry Kenworthy via use-livecode
<use-livecode@lists.runrev.com> wrote:
Simplest way – In card 1 of main stack to build:
on closestack
--- curryk 2020 no-purge LC build:
if the environment is "development" then
lock messages
--- and only if add'l main stack issues:
try
# delete stack "XYZ"
end try
end if
end closestack
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
