Re: lingo-l Member.erase()

Hi all you Adobe Director fans... Documentation under erase() method states: For best results, use this method during authoring and not in projectors. Using this method in projectors may cause memory problems. My question is, what kind of memory problems in the projector, and is it always fatal?

Re: lingo-l Member.erase()

At 11:53 AM -0400 4/19/05, you wrote: Hi all you Adobe Director fans... Documentation under erase() method states: For best results, use this method during authoring and not in projectors. Using this method in projectors may cause memory problems. My question is, what kind of memory problems in

RE: lingo-l Member.erase()

Thanks, Buzz (and Alexx). That's sort of what I've decided to. I've got a placeholder bitmap that I'm just changing the image of. If you really need to do it, working within an external castLib using saveCastLib periodically may clean up the issues. Regards, - Michael M. [To remove

RE: lingo-l Member.erase()

Thanks, Buzz! That's a great tip. - MM If you use importFileInto repeatedly, that will chew up memory in the same way. use 'set the filename' (or the modern syntax) for better memory management [To remove yourself from this list, or to change to digest mode, go to

RE: lingo-l Member.erase()

Thanks, Buzz (and Alexx). That's sort of what I've decided to. I've got a placeholder bitmap that I'm just changing the image of. Why erase()? Unless I'm missing something, can't you just use member().filename? [To remove yourself from this list, or to change to digest mode, go to