on 6/3/01 5:29 PM, Roy Pardi at [EMAIL PROTECTED] wrote:
> One easy culprit for a "leak" these days is the use of imaging lingo
> on bitmap cast members. If you change a bitmap member, it won't get
> unloaded because it has been modified. Do this enough and memory will
> get fragmented and "leak"
Thanks, but NO imaging Lingo is this project. Good suggestion though.
L8R,
JRS
===========================================================
John R. Sweeney Jr. ([EMAIL PROTECTED])
Interactive Multimedia Developer/Digital Media Specialist
OnDemand - Interactive, Inc. (www.ondemandinteractive.com)
P.O. Box 95811 847.310.5959 (office/fax)
Hoffman Estates, IL 60195 847.651.4469 (cellular)
===========================================================
[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!]