destroystack/destroywindow not working?

[Craig Newman]

I have seen this on Mac forever. I actually do not believe the “destroy” family of features does anything at all.

Craig

> On Mar 21, 2022, at 8:21 AM, Klaus major-k via use-livecode <use-livecode at lists.runrev.com> wrote:
> 
> Hi all,
> 
>> Am 21.03.2022 um 12:46 schrieb Klaus major-k via use-livecode <use-livecode at lists.runrev.com>:
>> 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?
>> 
>> Thanks for any insight!
> 
> looks like this is an IDE "feature"!?
> 
> I just noticed the menuitem -> Close and remove from memory
> Go figure! :-D
> 
> 
> Best
> 
> Klaus
> 
> --
> Klaus Major
> https://www.major-k.de
> https://www.major-k.de/bass
> klaus at major-k.de
> 
> 
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode