Removing a stack from memory - is this a bug?

[Joe Lewis Wilkins]

According to the Documentation Library, you probably should be using  
the delete file command as per:

If the stack is a main stack, the delete stack command removes the  
stack from memory. (Any unsaved changes are lost.) However, it does  
not remove it from the user's system. To delete a main stack, use the  
delete file command instead.

I can't imagine your wanting to allow one of your users to actually  
"delete" a stack. That is pretty dangerous. Of course, if they  
created it, that's a whole new concern. Better it should be done out  
of your application at the "Finder" level. Of course, I just jumped  
into this and you may well have a good reason for doing what you're  
discussing here.

Joe Wilkins

On Dec 27, 2006, at 9:54 AM, David Bovill wrote:

> Yes - that dialogue is a nightmare.
>
> Constellation has a nice viewer for all the stacks and their states  
> - but
> this is not an issue of organising as far as I can tell - it is  
> simply not
> possible to delete this stack...
>
>  delete stack "View|Movie|Player"
>
> Closes the stack but does not remve it from memory - it is still  
> loaded. All
> the destroy properties are set right (not that that should matter with
> destroy)...
>
> It is something that has happened before - so Id like to get to the  
> bottom
> of it. Most probably quitting and restarting Rev will fix it - but  
> then I
> loose the why it wont work thing.
>
> I got a strage clue in the message box:
>
>  delete stack
> "View#####REVEXCLUDEDSTRING#####Movie#####REVEXCLUDEDSTRING#####Player 
> "
>
> Seems it may be the name?
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your  
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution