Plug ins in MC 2.6b1

[Robert Brenstein]

>The files need to be read in order to check properties, but if the 
>destroyStack is set to true they should not remain in memory after 
>that.  If not it's either a bug in my code that I overlooked (I try 
>to keep things RAM-lite 'cause I know how you are <g>) or a bug in 
>the engine.
>
>Lemme know if you find any stacks hanging around with the 
>destroyStack true and I'll see what I can do.
>
>--
>  Richard Gaskin
>  Fourth World Media Corporation

Actually, this brings up a more general issue: should the Plugin 
Manager set the custom properties inside the plugin stacks OR should 
it keep that info in its own private list? My first inclination was 
to set them in the plugin stacks as it is in the current 
implementation. However, on second thought, these properties are only 
for benefit of the Plugin Manager, so it might be more appropriate to 
leave the plugin stacks alone. This way, we have more flexibility how 
to handle things and also reduce compatibility issues for the future. 
And this will eliminate any need to load stacks that are not 
explicitely requested to be opened. Granted, the downside is that 
library stacks have to be explicitely set for each new version. But 
that is how things have always worked with Extensions Manager under 
MacOS.

Robert Brenstein