The question now is, how do files in the library can become so corrupted? This would help to avoid it I hope.
On Wed, Jul 23, 2008 at 1:31 PM, Steven Sacks <[EMAIL PROTECTED]> wrote: > Welcome to the seedy underbelly of Flash development. > > What you've got here is the case of a corrupted library item. It happens > sometimes and there's only one thing you can do about it. > > Not too long ago, my team inherited a Flash 8 file with a corrupted library > item that was so terribly corrupted, the Flash 8 file would only open in > Flash CS3 on an old G4 Mac running OSX Jaguar. Yes, it was that specific > (We assumed that the original file was probably built on that system spec). > It would not open in Windows Flash 8 or CS3, it would not open on any Mac > Flash 8 or CS3 running a version of OSX higher than Jaguar. > > What we had to (and you have to) do is go through your library symbols one > by one, deleting each one until you find the sucker, and then replacing it > if need be. Thankfully, you can open your file directly. We had to open > the file in Flash CS3 (which is bloated and slow) on that slow old Mac with > 256MB RAM, delete a symbol, save as a new Flash file, copy said file to the > network drive, and try to open it from another computer, rinse repeat, until > we found the graphic that was causing it. It took us a few hours. > > Good luck! > > _______________________________________________ > Flashcoders mailing list > [email protected] > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > -- ...helmut _______________________________________________ Flashcoders mailing list [email protected] http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
