On May 26, 2004, at 10:21 PM, Irv Kalb wrote:
Is there any reason why these images must be all imported into Director? It might be easier to deal with these images if you had them all as external images in a single folder. Then you could have one (or more, depending on what your needs are for the catalog) graphic members that link to an external file.
To set this up, you import one image, which could just be a blank image, and select Import Link only (or what ever it is called. Then at run time, you build up a string of what the real file name is, and set the filename of the member.
Or, if you are looking to "protect" the content, use Director to put the image content into an embedded database. Arca, for instance. Arca even has a free image import tool you could use to batch catalog them, which works very well.
The actual problem sounds like a memory issue. Using a database should remove that, as well as make the overall application perform better. Why you are getting a memory issue from the import, is tough to say.
-- Troy RPSystems, Ltd. http://www.rpsystems.net
[To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/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!]
