RE: [Flashcoders] .aso cache frustration
>>Are you sure you just haven't written another class with the >>same name higher up in the include paths? Not sure if the last three responses are just due to list lag, but thanks - I solved it about 3 1/2 hours ago. Appreciate it though. :) Jason Merrill Bank of America Global Technology & Operations Learning & Leadership Development eTools & Multimedia Team ___ [email protected] 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
RE: [Flashcoders] .aso cache frustration
The other gotcha relates to shared libraries. If you are using a shared library you must republish that before you publish your primary swf. Laurie Jensen -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Merrill, Jason Sent: Wednesday, 21 March 2007 3:04 AM To: [email protected] Subject: [Flashcoders] .aso cache frustration 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 ___ [email protected] 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 ___ [email protected] 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
Re: [Flashcoders] .aso cache frustration
Are you sure you just haven't written another class with the same name higher up in the include paths? > > From: "Merrill, Jason" <[EMAIL PROTECTED]> > Date: 2007/03/20 Tue AM 11:03:32 CST > To: [email protected] > Subject: [Flashcoders] .aso cache frustration > > 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 > > > > ___ > [email protected] > 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 > -- John Mark Hawley The Nilbog Group 773.968.4980 (cell) ___ [email protected] 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
RE: [Flashcoders] .aso cache frustration
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: [email protected] 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: [email protected] >>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 >>> >>> >>> >>> ___ >>> [email protected] >>> 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 >>> >>___ >>[email protected] >>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 >> ___ [email protected] 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 ___ [email protected] 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
RE: [Flashcoders] .aso cache frustration
Ian, thanks! Actually, I thought it was the case that my first .swf didn't load in the same class, but turn out it does - I recompiled both and the .swf updated fine. Thanks for the suggestion, I would have never thought of that! 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: [email protected] >>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 >> > ___ [email protected] 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
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: [email protected] >>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 >>> >>> >>> >>> ___ >>> [email protected] >>> 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 >>> >>___ >>[email protected] >>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 >> ___ [email protected] 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
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 ___ [email protected] 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 ___ [email protected] 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
