At 03:43 29.05.2002 -0700, you wrote:
>I currently have a database setup which pulls jpegs into Director as
>bitmap type at runtime. The amount that is loaded into the cast depends
>on search results (sometimes 100-600 thumbnails). Each thumb nail is 2K
>on disk but in Director as bitmap type is 60K. When I have to load
>about 150 thumbnails from disk the Director program is eating up a
>couple hundred megs of memory (according to ctrl-alt-tab in windows XP).
why are you importing 100-600 thumbnails? Do you need them all
at the same time on the stage? If not, just load the ones you need
dynamically when needed and unload / delete the ones you don't
need anymore.
The decision whether to store the pictures in the db depends on
various requirements. If you prefer to have them all stored in a single
file, need fast access, don't want to bother with filenames and directory
paths etc. then store them in Valentina. If you need to dynamically
load an unknown amount of pictures from the outside (i.e. updated
by someone else, who puts the picts into the folder), and don't want
you get a huge database blob file, use the external picts.
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.
/at/ Ruslan:
Whatever happened to the plans to add the image object functions SetImage()
/ GetImage()
to store image objects in a picture or media field?
Martin DOT
Martin Kloss
Like the author? Buy the book at:
http://www.amazon.de/exec/obidos/ASIN/3898422194/lingmmugd
Experience the possibilities....
http://www.go-shockwave.de
Get your daily dose of Lingo at the LingoPark:
http://www.lingopark.com
©2002 Martin Kloss |
