"Edwards, Waverly" wrote: > If you've come anywhere near 16megs in an application, I think you should > reconsider how your app is done. I think I'd put any large resource(s) in > its own file, open the resource fork and start reading. An app should only > be as large as necessary. An app that's 10,12,14... megs must have some > really large resources and probably should be in their own file. Absolutely correct, which is one of the reasons I want to list this kind of thing as a limitation. My first encounter with it - adding a bunch of music to a resource file, one at a time with SoundEdit 16, caused me to loose the better part of a days work as the whole thing came crashing down - and I hadn't the slightest idea why. Maybe I should have known, but sometimes we barrel along into a project doing things as they come, easily until we encounter something like this. I not only lost the day's work, but the confidence that I knew what I was doing. (Which may have been a good thing!) I haven't been quite so careful with my PICT Resources, and there may come a time when I need to be concerned there as well. Thanks Ed, Joe Wilkins > -----Original Message----- > From: Joe Lewis Wilkins [mailto:PepeToo@...] > Sent: Sunday, April 02, 2000 7:05 PM > To: futurebasic@... > Subject: Re: [FB] Re: FB^3 Limitations > > Brian Jones wrote: > > > >one needs to be concerned, I think we should mention them. For example: > > >I'm sure there are limitations to the number/size of a single resource > file, > > >somewhere about 12 MBs as I recall. I realize "these" kinds of > limitations > > >are Macintosh more than FB, but they affect the use of FB, so should be > > >spelled out - IMHO. > > > > This is actually a 16 MB limit, although at file sizes approaching 16 MB > > data can begin to be corrupted. > > Which brings up a good point. Since FB^3 "completes" the Resource file for a > Project, adding the final touches, if you will, does FB^3 check to see that > this limitation, what ever it "should be", is never exceeded?