Home Tutorials Forums Articles Blogs Movies Library Employment Press
Old 07-07-2009, 06:57 PM   #1
Flash Gordon
rather be programming
 
Flash Gordon's Avatar
 
Join Date: Feb 2005
Location: City of Angels
Posts: 10,140
Default External Actionscript Classes Version Conflict

Scenario:
  • swf B compiles with class Vo in it and displays it's values
  • swf A compiles with a revised version of Vo in it and loads swf B

Result:
swf B shows swf A's revised Vo class properties and not the version it got compiled with even though nobody told swf B to change it's Vo properties.

Has anyone encountered these kinds of situations? How is everyone dealing with this?

[EDIT] Since the forums still seem to be broke, you can grab my sample files here. Compile B.fla and then change class Vo version property and you'll see when you compile A that B display's the new Vo version. Link to Files
__________________
trace("Good bye Flash.") Log.i(TAG, "Hello Droid");

Last edited by Flash Gordon; 07-07-2009 at 07:05 PM.
Flash Gordon is offline   Reply With Quote
Old 07-07-2009, 06:59 PM   #2
Tilpo
Watermelons are gansters
 
Tilpo's Avatar
 
Join Date: Aug 2008
Location: Hilversum, The Netherlands
Posts: 215
Default

I don't really know what you mean, but often when changing files that are already uploaded people can use xml to alter the data inside, or simply replace the file. What do you mean? Please specify!
__________________

hoc postum continuit nudilo appendo
This post was touched by his noodly appendage.
Tilpo is offline   Reply With Quote
Old 07-07-2009, 09:02 PM   #3
Flash Gordon
rather be programming
 
Flash Gordon's Avatar
 
Join Date: Feb 2005
Location: City of Angels
Posts: 10,140
Default

no. I'm talking about ApplicationDomain issues.
__________________
trace("Good bye Flash.") Log.i(TAG, "Hello Droid");
Flash Gordon is offline   Reply With Quote
Old 07-08-2009, 01:47 AM   #4
maskedMan
Obfuscated Coder
 
maskedMan's Avatar
 
Join Date: Apr 2008
Posts: 1,571
Default

I've encountered this many times. Usually we only recompile swf B if some aspect of the new version of the class file residing in swf A causes things to break.

Sometimes you can use this behavior to your advantage, though. For example, if you know that changes to class Vo must be made across the board, but that no interactions with Vo must be changed in the B level swfs, all you would need to do is compile the changes into A and then not worry about the loaded children... at least not until you are forced to have them stand alone.
__________________
http://www.scriptocalypse.com - It's not the end of the world. It's just Actionscript!

man.mask = mask_mc;
maskedMan is offline   Reply With Quote
Old 07-08-2009, 02:21 AM   #5
Flash Gordon
rather be programming
 
Flash Gordon's Avatar
 
Join Date: Feb 2005
Location: City of Angels
Posts: 10,140
Default

Yea, it looks like there is no way around my problem. I could "partition" the swf by loading B into a new ApplicationDomain() and then that behavior won't happen, but then I can't type B to IB anymore: I lose my interfaces. Sigh.....I don't know if it's a limit of my knowledge of domains or if it is just the way it is. Follow me?
__________________
trace("Good bye Flash.") Log.i(TAG, "Hello Droid");
Flash Gordon is offline   Reply With Quote
Reply


Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT. The time now is 06:19 AM.

///
Follow actionscriptorg on Twitter

 


Powered by vBulletin® Version 3.8.5
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Ad Management plugin by RedTyger
Copyright 2000-2013 ActionScript.org. All Rights Reserved.
Your use of this site is subject to our Privacy Policy and Terms of Use.