That's what I think... The Print Dialog is modal, so Flash should shut up and wait, not run ahead of itself doing all other manners of things (excuse the grammer)!
Lee -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Danny Kodicek Sent: 29 March 2006 14:08 To: Flashcoders mailing list Subject: Re: [Flashcoders] PrintJob causes Abort Script error message. > The PrintJob class has no idea if other scripts are in the middle of > something when it makes its synchronous call to the system, nor should it. > PrintJob can't make sure that there are no other scripts in the middle of > anything when it tells the browser to open a print dialog. It does what > it's told to do. It's up to the coder to make sure there isn't code that > would be adversely affected by Flash making a synchronous call. Actually, I don't really get your point here. Because Flash is single-threaded, it doesn't really mean anything to talk about 'scripts in the middle of anything'. There's precisely one script at any one time that's in the middle of anything. The size of the call stack should be neither here nor there when Flash is deciding if it's hanging. Danny _______________________________________________ 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
