I've seen this occasionally, where the mainstack is removed but the substacks are still in the
list of available stacks. I think the IDE list of stacks in memory isn't updated correctly
unless all substacks are marked as destroyed. At least, that's what it looks like.
On 3/21/22 6:46 AM, Klaus major-k via use-livecode wrote:
Hi all,
I have a stack with its destroystack/destroywindow
properties set to true.
When I close it and open another stack which has a
substack with ther same name as a substack of the
previous stack, I get this really annoying dialog:
"A stack with that name is already in memory..."
Shouldn't setting destroystack/destroywindow prevent this?
Or am I misunderstanding the meaning of these props?
--
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
