On 2021-10-07 20:12, Pi Digital via use-livecode wrote:
Quite right. I make sure it’s the main stack selected and that all
other stacks, inspectors and editors are closed just in case. Then, as
you have it laid out in steps 2 to 4 and 4 and 4 ad infinitum. :)
That’s all there is to it.
There is nothing, as I am aware, that is loading any other external
stacks at all. They only reference to substacks of the main.
What do we check next?
So we need to try and work out what is causing the load of a stack with
the same name of that in memory (my hunch is that there is a filename
reference to a stack somewhere, which is being triggered, and reloading
the stack which has just been saved-as from it original location).
If you:
edit script of stack "revbackscriptlibrary"
Find the `reloadStack` handler and then add:
put the executionContexts
At the very top of the handler - then you should get the backtrace of
what handlers are executing at the point the reloadStack message is sent
which should help pinpoint the culprit.
Warmest Regards,
Mark.
--
Mark Waddingham ~ [email protected] ~ http://www.livecode.com/
LiveCode: Everyone can create apps
_______________________________________________
use-livecode mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
