I'd probably say recompile both SWF's. What could be happening is the
classes inside swf A imports one or more class that swf B has.



-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Merrill,
Jason
Sent: Tuesday, March 20, 2007 11:08 AM
To: flashcoders@chattyfig.figleaf.com
Subject: RE: [Flashcoders] .aso cache frustration

Close - 

.swf B gets loaded into .swf A

.swf B has the trouble - however, .swf A does not import the same
classes .swf B does.

Jason Merrill
Bank of America  
Global Technology & Operations
Learning & Leadership Development 
eTools & Multimedia Team


 

>>-----Original Message-----
>>From: [EMAIL PROTECTED] 
>>[mailto:[EMAIL PROTECTED] On Behalf 
>>Of Ian Thomas
>>Sent: Tuesday, March 20, 2007 1:16 PM
>>To: flashcoders@chattyfig.figleaf.com
>>Subject: Re: [Flashcoders] .aso cache frustration
>>
>>Hi Jason,
>>   It's not because you're loading the SWF into another SWF 
>>which has different/older versions of classes with the same 
>>name and package, is it..?
>>
>>HTH,
>>   Ian
>>
>>On 3/20/07, Merrill, Jason <[EMAIL PROTECTED]> wrote:
>>> So I am updating an AS 2.0 class file I wrote last fall, 
>>and when I go 
>>> to publish the .swf, I get the classic problem where the 
>>.swf doesn't 
>>> update with the new code in the class.  I verified it by commenting 
>>> out everything but the constructor which only contains the 
>>trace statement.
>>> So I figured, it was just a simple matter of deleting the 
>>.ASO files 
>>> because Flash was still caching my old .as file. But no 
>>luck.  I also 
>>> verified all my classpaths were correct and pointing to the right 
>>> parent directory where the class file lives as a package.  The only 
>>> way I can get the new code to get injected into this .swf 
>>is to name 
>>> the class and file something else completely different and 
>>then import 
>>> that into my .swf instead.
>>>
>>> Has anyone fixed this issue before? (and please don't tell 
>>me to use 
>>> MTASC instead - had enough problems with that which I plan 
>>to tackle 
>>> later :) )  Deleting ASO files (at least from the Flash 8 
>>IDE option) 
>>> doesn't seem to do the trick.  Do I need to manually hunt 
>>down these 
>>> old .aso files?  Thanks.
>>>
>>> Jason Merrill
>>> Bank of America
>>> Global Technology & Operations
>>> Learning & Leadership Development
>>> eTools & Multimedia Team
>>>
>>>
>>>
>>> _______________________________________________
>>> 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
>>>
>>_______________________________________________
>>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
>>
_______________________________________________
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

_______________________________________________
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

Reply via email to