Hi Slava
Everytime you create a new member, director needs to store that information
somewhere, the same goes for a modification of the castmember and or the
castlib or movie in general. Those changes are therefore stored in memory
and the memory released when the castlib is changed. In general, I would say
that if you create, use and erase a castmember during a session your
probably going to be okay (unless your doing some 20 mb image file or
something) but if you are creating thousands of cast members and your
enduser is running in extremely limited memory space, then yes you could
approach entering a problem zone. If you need to remember user settings, and
those settings will be stored in a constant text member, then you could use
something like the propsave xtra to save the media of the member to an
external list member or some such thing. You might even be able to store
media of a member in a property list or linear list and then grab it and
apply it to a dedicated castmember. Not sure if that is any safer or less
memory intensive then creating and erasing a castmember on an as need basis.
Sincerely
Mark R. Jonkman
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/LUJ/lingo-l.cgi To post messages to the list,
email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED])
Lingo-L is for learning and helping with programming Lingo. Thanks!]
