Yep - that works perfectly well. But it's always better to avoid situations like this:
Some of the developers used the same classes and slightly modified them for their needs.
by assigning different package names to different modules, if you know they'll all be running in the same 'container' app. (Apart from shared utility classes and the like, which you shouldn't be rewriting the behaviour of every time you alter them...)
Ian On 5/4/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
The way I understand it, classes are loaded as global variables. You can see them when you test the movie and click Debug-->List Variables. I was on a project with multiple developers. The Shell loaded many different swf files. Some of the developers used the same classes and slightly modified them for their needs. The issue was that the class paths were identical, but even though they were used in separate swf files Flash would not replace the first loaded class with the new ones from the newly loaded swf files and cause the file to "break". This only happens if the class path is the same. Also, after using the app for a while you can check the "List Variables" again and see that Flash had amassed every class ever loaded. I ended up writing a Class Cleaner class to delete the global class variables and it works. It fixed the broken program files. I don't completely understand the details of Flash's garbage collection, but this solved my problem. I based my class after the idea that I found here: http://www.helpqlodhelp.com/blog/archives/2003_04.html
_______________________________________________ Flashcoders@chattyfig.figleaf.com To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com
