on 2/27/02 11:01 AM, Andreas Gaunitz P11 at [EMAIL PROTECTED] wrote: > Eva, > > >> Could it be a memory issue? It seems strange that 3-5 images work fine in >> one of my gallerys but exceeding that number so far has always given me the >> error. > > I also find it strange, and I don't thjink it's likely to be a memory > issue, beacuse you aren't straining the computer very hard. If you > had 200 images then I would be more anxious.
I do have this many images if not more however, no gallery exceeds 15 images and each gallery is in a seperate linked director movie. > > Do you get exactly the same symptom if you rearrange the order of the > members in the images cast? If it always complains on member 5, what > happens if you put member 5 first? It doesn't seem to be catching on any particular image. It seems to be directly related to the volume of images. For example initially the smaller galleries work fine but if I continue through and look through the other galleries (granted the larger galleries post the previously discussed error message.) and I come back to the smaaller galleries that were working before they proceed to sieze up too. > > Does it always complain on exactly the same image member, or is > somewhere between nr 3 to 5 in the same movie? > > Did you try to remove all image members and insert a different set of > images, for example only the images that work from each movie? Do > some of the imported images or their members have strange characters > in their names? Sorry, but we have to narrow down the problem here... > > >>> Two, are you using jpegs? >> >> Yes > > All RGB jpegs, or some RGB some CMYK? Please do try to resave and > reimport them in another format: Mac RGB pict, Win RGB bmp. For some > reason I think this will solve, or at least reveal, the problem. I double checked all images jpeg/RGB. With the volume of images I am dealing with I think the smarter thing to do at this point is to backtrack and code it without imaging lingo for now. > > >> Double checked the xtra folder .jpeg import xtra there. >> My members are 32 bit and I am pretty sure I changed his display member for >> all of the movies. > > Which Xtras folder did you double check? Director's or the movie's? > If the movie's: Why don't you include Xtras in the projector instead? I always keep an external folder within my project for all of my xtras to eliminate overhead by having them in each individual movie. > > Another thing: You are using the JPEG import Xtra. This was a part of > the Director 7 package, and is obsolete in D8+, as jpeg fuctionality > is built-in. (No Xtra needed as long as you only use jpeg.) But in D7 > there was no imaging lingo... !? You are right the two xtras I was looking at were .jpeg agent and .jpeg export neither of which I should need. > > I'm speaking about Mac here, still not sure what platform you're on, > and if the Xtras might be different on Win (though I wouldn't hink > so). I am on a mac too for reference. > > > BTW: is the code from lesson 1, used for importing external files, > included in your project? If so, there might be a problem when > Projector tries to load external files from an empty or non-existent > folder, especially if the folder contains something else than an > image. Delete the folder and create a new one with the same name and > location! Again I am not using lesson one but two. All of my members are held in internal casts not relative path folders. Thanks... -Eva > > > HTH > -A. > > [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!] > [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!]
