Well, there IS a workaround but you have to hack your swf using flasm and set the timeout to some larger number. This really is not recommended and most people use this to actually decrease the timeout delay, not increase it (because they're simultaneously increasing the recursion depth).
http://codeazur.com/forum/viewtopic.php?t=260 http://www.actionscript.org/forums/showthread.php3?t=65371 http://www.powersdk.com/ted/2005/11/macromedia-please-add.php > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf > Of Steven Sacks > Sent: Wednesday, March 29, 2006 2:58 AM > To: 'Flashcoders mailing list' > Subject: RE: [Flashcoders] PrintJob causes Abort Script error message. > > PrintJob is a poorly written class in general. Also, it runs > synchronously > when it talks to the system. The reason Flash throws up the alert is > because for 15 seconds it is stuck waiting. The movie is > waiting on a line > of code to finish. Flash responds to the movie being hung, which it > technically is because the request to the OS is synchronous. > > There isn't a workaround except to not use PrintJob. > > > > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On Behalf > > Of [EMAIL PROTECTED] > > Sent: Wednesday, March 29, 2006 2:38 AM > > To: flashcoders@chattyfig.figleaf.com > > Subject: [Flashcoders] PrintJob causes Abort Script error message. > > > > > > Apologies for reposting, hopefully someone has come across > > this before. > > > > We have a large and complex Flash RIA that represents almost > > 2 years of development effort. Unfortunately we have one > > major unresolved issue. In a couple of places we have print > > functionality. When the print job system dialogue appears, if > > the user doesn't close the dialogue within 15 seconds, the > > Abort Script message appears ("A script in this movie is > > causing Macromedia Flash 8 to run slowly. If it continues to > > run, your computer may become unresponsive. Do you want to > > abort the script?"). > > > > Is this a known Flash bug? > > Is there a workaround? > > We've been trying to solve it for about a month. > > > > ta. > > > > _______________________________________________ > > Join Excite! - http://www.excite.com > > The most personalized portal on the Web! > > > > > > _______________________________________________ > > 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
