I have explained in detail the source of your problem. If you choose not to take the advice given to you by coders who know more than you about the subject at hand, then why post a question to the list? You are doing yourself and your client a disservice with your blame Macromedia attitude and finger pointing.
It's not the end of the world. Your code simply does not take into account a synchronous call. That is not PrintJob's fault. That is not the Flash player's fault. You should fix your code now that you understand why it's breaking. The fact is, there's a real solution to your problem. Whether you realize it or not, you have already admitted that it is your code that is to blame. You have stated twice now that the application is a real-time trading system. In all likelihood, this means you have intervals running and all kinds of parsing and drawing going on most of the time. The exact kind of processes that would go haywire should Flash have to make a synchronous call with an indeterminate response time. PrintJob makes a synchronous call and Flash is single threaded. All your real-time stuff is reacting to the synchronous call. When a user presses the print button, you need to put a halt on new processes, wait for currrent processes to complete and then start the PrintJob. If it's going to take more than 250ms, throw up a window that says something like "Preparing to print". Upon completion of the PrintJob, you need to resync with the server immediately, and should probably put up a window that says something like "Sending data to printer" until the application is all caught up. Your SLI injection to increase the timeout as a solution is irreponsible. It is a heavy-handed technique fraught with potential problems far worse than your printing one and it doesn't actually solve the problem, it just masks it, and poorly. I wouldn't go live with that. "Do the right thing." - Spike Lee > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf > Of [EMAIL PROTECTED] > Sent: Wednesday, March 29, 2006 4:40 AM > To: flashcoders@chattyfig.figleaf.com > Subject: Re: [Flashcoders] PrintJob causes Abort Script error message. > > > >> Danny Kodicek...I think I remember you from my Director > days, so long ago.That's me. And I remember that you were a > bit belligerent then too ;)Danny > > > Ahh yes, the old Direct-L days... sigh. > > Update: that hack gets it up to about 1 min 20 before the > alert appears instead of around 20 secs. Not ideal, but what the heck. > > I can't "fix" code which ain't broken. 50,000 lines of real > time trading system works perfectly. One call to PrintJob and > it all goes horribly wrong. Its a Flash Player / PrintJob > issue.If Macrobe want Flash to be taken seriously as an RIA > platform issues such as this need to be fixed before > Microsoft gets us all writing C#..... > > _______________________________________________ > 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
