Hey Hans, are you talking about a situation where ClipA would still be running but you might introduce a new ClipB at runtime?
IE: like, if you had a multiplayer game running, and you updated one of the avatar's swf's - you want that new SWF's code to be loaded and used without restarting the app for everyone is that what you're talking about? On 11/6/06, Hans Wichman <[EMAIL PROTECTED]> wrote:
Hi list, you've probably had this scenario before, you are loading clip B into clip A and B defines some classes. Now you change B's classes, recompile and reload it into A, but since the old classes are still there, B wont function as it should, unless you restart A. Now I can remove the classes from memory and force a reload, but I was wondering if this is an 'accepted' thing to do, in other words, will it get me into trouble or not:)? I'd like to hear your thoughts on this. greetz JC _______________________________________________ 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
-- [ JPG ] _______________________________________________ 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
