destroystack wrong behavior...

[Thierry D.]

> Hi Thierry,
> 
> Yes, I am having the same problem.
> Once in a while, even after explicitly deleting a stack with the delete command,
> the stack still pops up somehow.

Thanks Mark

I'm not alone !  Half the suffering is gone :)

> 
> I think this is due to the compexity of the IDE. Probably, the IDE team has used the long ID of a stack in several places, instead of the short name of the stack. If this reference to the long ID of a stack stays in memory, then the IDE will be able to find the stack even after it has been removed from memory.

As I have only one stack and a substack within
 can't see the "long-id-stack" virus from my side. Agree ?


> I don't think there is a quick solution for this problem,
> besides quitting and re-starting RunRev.

Hmm, so I have to put a Red Banner for my customers :(

> Of course, it is also possible that the long ID of a stack is still available in one of your own stacks.
> You might want to make sure that these references are not there.

I'll check again...

Regards,
Thierry

>> Hi all,
>> 
>> from time to time, in Rev IDE ( 4.0 MacOS ) when closing a stack,
>> the stack is still in memory, seen in the Application browser too.
>> 
>> DestroyStack and DestroyWindow are set properly !
>> and Yes, I refresh the application browser.
>> 
>> It had happened few times during my developments,
>> and never I could find a solution ?
>> More, sometimes, it works again after
>> a while without being able to know why.
>> 
>> Does it sound familiar to someone and
>> any idea what could cause this wrong behavior ?
>> 
>> Regards,
>> Thierry