On 5/14/21 2:49 PM, Marty Knapp via use-livecode wrote:
When you close a stack that has its destroyStack set to true, it should not remain in memory. In my case it
also seems to get stuck as the default stack. Even if my preference stack did not remove from memory as it
should, specifically going to stack "XYZ" and setting it as the defaultStack, one would expect
"this stack" to be be "XYZ" but it is not.
As mentioned I am now querying revLoadedStacks and manually deleting from
memory the preference stack and that seems to have taken care of it. But it
makes me nervous that the same issue may unexpectedly arise elsewhere in my
code. This is an app that has been working fine for years and this has not been
an issue till now.
I agree this should work but until it does, a workaround might be to use "the topstack" rather
than "this stack".
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
_______________________________________________
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
