Hi mb,
>At 2K for each thumb I never expected there to be such a memory problem.
>I actually am doing all the drawing via imaging lingo already. I never
>considered pulling images on the fly from Valentina because I thought it
>couldn't be faster than loading them internally, and why introduce a
>possible speed hit. Now that speed hit (if there is one) might
>definitely be the lesser of evils =)
The amount of memory you really(!!!) need to show your thumbs just
depends on the size of the screen.
There is only one bitmap that must stay in memory when you show your
thumbs and this is (the stage).image. You can use
vCursor.GetPicture() on just a single castmember and only retrieve
the thumbs that are visible on stage at the current time. After
copying the image you should dereference it completely i.e. by
overwriting the same variable with the next thumbs image.
You definitely wont use hundreds of MB of memory as long as you work
in a clean way.
Don't keep references to you thumb images i.e. by storing all the
images within a list, you don't need it. Maybe there's a performance
reason to keep the images of the currently visible thumbs in a list
(and so in RAM).
There is also a difference between the fileSize and the memory
needed to show a picture. To load a compressed JPEG image Director
will need at least
(theImage.width* theImage.height*theImage.depth) Bytes
independent of the grade of compression (because Director must
uncompress it to show it).
>I don't get what Director is doing. I even brought all 6000 2K each
>thumbs into an external cast and this cast is now 220MB (after save
>compact, etc)! I'm referring to the file size on disk. Am I missing a
>special lingo method like cleanUpFatGarbage() ? =P I just didn't expect
>these type of problems when I started =)
Use "Publish" or "Update Movies..."
--
Greets Tsch.
---------->
on stopMovie
mRemember gRealLife
updateStage
no end
©2002 Tschoatscho Kettl |
