I have had this problem when more than one swf is tied to a class. Say you have a Bears and a Dolphins swf which both use the football class, you make changes to the football class and compile the Dolphins swf, but you do not recompile the Bears swf. The Bears swf loads before the Dolphins swf and you do not see the code changes.
P.S. This also happens when you have a class that is extended by other classes, in other words it is shared by the swfs that are extending it. For instance, you have a Team class that is extended by Bears and Dolphins... I think you get where I am going with this, if not let me know. Hope this helps. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Pete Hotchkiss Sent: Monday, November 14, 2005 4:36 PM To: 'Flashcoders mailing list' Subject: [Flashcoders] Cached Class instance I've stumbled across something of an annoying bug in Flash 8. It's difficult to accurately re-create but it's realy starting to p**s me off. I'm creating an app that has a base Application class that loads .swfs into a movie clip instance. Each of these swfs have bunch of stuff it, some of which talk back to the base app class. Nothing new there. However, lets say on of these .swfs loaded in has an instance of a class, lets call it football. I code a bunch of stuff for this class compile it into the swf, and all works. Then I test loading this football.swf into my base app. It all works fine there also. So I carry on making a bunch of changes to my football swf, mostly code but some visual changes. I re compile the football .swf, and local I see all the changes. I load it into the base app swf and all works ok. Lets say I have several rounds of this. Change > Test > Change > Test etc etc. Ok you get the picture. No at some point, and it's completely in consistent when it occurs, the base app decides it's going to ignore any CODE changes you make to your football class. It just stubbornly ignores any change you make. If I test the football.swf locally, the code changes are displayed and all works. It's just when loaded into the base app it falls over. And here's 2 crazy things - I know it is DEFINITELY NOT cacheing the swf as any visual changes in the football.swf are reflected in the swf that's loaded into the app. It's only code that is ignored. More interestingly, if I go - SOD THIS FOR A LAUGH - a re-code the class verbatim - with a new class name (not instance name but Class name) the new code changes work when loaded into the base app. Truly very weird. And it gets weirder. This has been occurring ALL day - so I've been through about 6 rounds of class name changes - and I've run out of suitable names. So I go back to the ORIGINAL class name, and hey presto - code that must be 4 hours suddenly appears when running the base app. Ok - so I've tried the following. Re-starting Flash ... Makes dito of a difference Copying the Files to a local drive (I recall hearing a problem compiling over a networked drive) Renaming the FLA's About the only thing I haven't done is restart my machine - but it just aint practical to do that every 40 mins or so. So question. Has anybody else seen this behavior before? Have I inadverntaly pressed some inadvertently key combination (CTRL-SHIFT-ALT-Q-W-E-R-T-Y) that triggers a cache option in the compiler ? This is a Win2k box - with buckets of ram. Frustradedly Pete _______________________________________________ Flashcoders mailing list [email protected] http://chattyfig.figleaf.com/mailman/listinfo/flashcoders _______________________________________________ Flashcoders mailing list [email protected] http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
