> In my experience, I have always decided to store the pictures, even
> large ones in Valentina, because the it way easier to handle and there's
> no way for people to mess with the picts from outside the application.
Just a note here because I think I found a bug in Director relating to
manipulating pictures from outside of director. Here is a snippet of my bug
report to Macromedia. I would love to here feedback from others here if they
can confirm/refute this...
Bug Description:
Using Member.filename produces memory leak
=======================
Summary:
Steps to Reproduce:
1. Place a bitmap on the screen that will be replaced by external files (5
bitmaps in my case) by using the member(myMember).filename = (path &name of
external file) command
2. Set up a loop so that the bitmap is replaced the external files of the
same size one at a time. Loop through the logos many times.
3. I created a MIAW that showed the Initial freebytes and the current
freebytes to monitor memory usage. (only the current freebytes updated)
4. Set the project running.
=======================
Expected Results:
Logos would cycle on the screen and no memory would be used.
=======================
Actual Results:
Logos cycle but the 20-40 bytes are lost with each changing bitmap. After a
short amount of time my project had eaten up 5 mb too many. My work around
has been to import the logos to an external cast at run time and manipulate
them from there. When I do this the above steps produce no memory loss while
the logos loop. If I had to guess, I think that when director reads the name
of the external file the memory is lost from the previous reading. That
would account for the variation in memory loss.
=======================
Platform: Both Windows and Mac
=======================
Sincerely,
Eric Curtis
www.rgbdesignstudio.com
©2002 Eric Curtis |
