Last week I went to launch a project that had been published for FP9, tested mostly in FP9, and then when we tested in FP10, we noticed a tragic difference... I was using the old "uncheck 'Export in First Frame' and put everything on a single keyframe on Frame 2" method of preloading. In FP9, it worked fine, but in FP10, I could hear all the movie clips that had sound looping endlessly, even though the movie stopped on frame 1 and skipped over frame 2 after loading. So, I am confused as to why these clips on the timeline were ever instantiated when the frame they existed on was never truly reached.
We ended up just using a parent swf to load the main movie and go back to everything "Export in first frame" which is arguably more elegant anyway, but I'm a little shaken by the last-minute discovery. Does anyone have a recommendation as to how to avoid this? Is there a more modern way to Export classes from the Library and keep them off the first frame so that accurate load progress can be displayed? (keeping the non-Flex, Flash IDE workflow in mind, please). -- -jonathan howe _______________________________________________ Flashcoders mailing list Flashcoders@chattyfig.figleaf.com http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
