Re: [Flashcoders] PrintJob causes Abort Script error message.
I have over 20 years of programming experience including at assembler level, advanced Java, etc, but thanks for trying to put me in my place :-) There is no error. There is no timeout. Not in the PrintDialog object. I think the FlashCoders list in general has a silly habbit of saying something like: does mc._xscale = 50 change the width? does anyone know this answer? and then half a week later, after pages of theoretical discussion, someone actually tries out the half-minute test. Try and do anything advanced (such as a stock exchange trading system) and it [breaks] ... That ain't an error with my code! is a DailyWTF-worthy comment. What does a stock exchange trading system have to do with the OS print dialog? I've never seen this error, in any version of Flash since 7 when it was created. I've created complex (2-year) systems where the sole product is a printed page from Flash. simple test. just a simple test Tyler ___ 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
Re: [Flashcoders] PrintJob causes Abort Script error message.
I agree with your sentiments Ron, that future designers of RIAs authored with Flash need to be aware of this issue. To clarify my own situation, I have inherited half-way through development an extremely complex system, that has just gone live with several thousand users. The system is a joint effort by several organisations. Roll-out has been exceptionally smooth. The printing functionality was one of the many late spec changes that the client asked for. As the system is composed of many V2-style components, many of which use interval timers to get around initialization issues, and has a lot of real-time financial data transfer going on in the background, setintervals, etc etc, that to reengineer it at this stage is totally out of the question. I believe that it is up to Macromedia to engineer the Flash player and the intrinsic classes that we developers can do nothing about, so that they work robustly and as expected. They could at least amend the documentaion for PrintJob to warn developers of the issues. --- On Wed 03/29, Ron Wheeler [EMAIL PROTECTED] wrote: From: Ron Wheeler [mailto: [EMAIL PROTECTED] To: flashcoders@chattyfig.figleaf.com Date: Wed, 29 Mar 2006 09:04:19 -0500 Subject: Re: [Flashcoders] PrintJob causes Abort Script error message. I would suggest setting the timeout to 7200 seconds and then test it to see what happens if you leave it sitting over lunch.Please warn us when you are going to do this, since from the tone of the conversation, there is some sense that this will cause the end of civilization as we know it.I suspect that the impact will be considerably less and the users of the application may be able to deal with any repercussions by changing their reaction to a dialogue box - it should not be taken as an invitation to go for a coffee.If Macromedia feels OK about the single threading issue, we have to cut ourselves some slack about dealing with it.It certainly is a cautionary note to designers of new applications that you should consider designing in some way to easily shutdown all of the animation and communication functions while setting up a print job. The effect on a communication link of an extended timeout might be one of the problems that you encounter since the other end might decide that you have died over lunch and cut its end. If you are re-establishing the link (authorization???) on each data transfer, this may not be a problem.RonRon/training.figleaf.com ___ 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
RE: [Flashcoders] PrintJob causes Abort Script error message.
As the system is composed of many V2-style components, many of which use interval timers to get around initialization issues, and has a lot of real-time financial data transfer going on in the background, setintervals, etc etc, that to reengineer it at this stage is totally out of the question. Well, it always sucks to inherit somebody else's bad work. I've done it many times, and almost always it would have been better to rewrite it myself (and sometimes I did). PrintJob has a ton of problems. It's a terribly written and poorly documented class. -Steven ___ 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
Re: [Flashcoders] PrintJob causes Abort Script error message.
Let us know how it all works out. Good luck. Ron [EMAIL PROTECTED] wrote: I agree with your sentiments Ron, that future designers of RIAs authored with Flash need to be aware of this issue. To clarify my own situation, I have inherited half-way through development an extremely complex system, that has just gone live with several thousand users. The system is a joint effort by several organisations. Roll-out has been exceptionally smooth. The printing functionality was one of the many late spec changes that the client asked for. As the system is composed of many V2-style components, many of which use interval timers to get around initialization issues, and has a lot of real-time financial data transfer going on in the background, setintervals, etc etc, that to reengineer it at this stage is totally out of the question. I believe that it is up to Macromedia to engineer the Flash player and the intrinsic classes that we developers can do nothing about, so that they work robustly and as expected. They could at least amend the documentaion for PrintJob to warn developers of the issues. --- On Wed 03/29, Ron Wheeler [EMAIL PROTECTED] wrote: From: Ron Wheeler [mailto: [EMAIL PROTECTED] To: flashcoders@chattyfig.figleaf.com Date: Wed, 29 Mar 2006 09:04:19 -0500 Subject: Re: [Flashcoders] PrintJob causes Abort Script error message. I would suggest setting the timeout to 7200 seconds and then test it to see what happens if you leave it sitting over lunch.Please warn us when you are going to do this, since from the tone of the conversation, there is some sense that this will cause the end of civilization as we know it.I suspect that the impact will be considerably less and the users of the application may be able to deal with any repercussions by changing their reaction to a dialogue box - it should not be taken as an invitation to go for a coffee.If Macromedia feels OK about the single threading issue, we have to cut ourselves some slack about dealing with it.It certainly is a cautionary note to designers of new applications that you should consider designing in some way to easily shutdown all of the animation and communication functions while setting up a print job. The effect on a communication link of an extended timeout might be one of the problems that you encounter since the other end might decide that you have died over lunch and cut its end. If you are re-establishing the link (authorization???) on each data transfer, this may not be a problem.RonRon/training.figleaf.com ___ 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
RE: [Flashcoders] PrintJob causes Abort Script error message.
Is this a known Flash bug? It's not a bug. Is there a workaround? You cannot change the timeout. We've been trying to solve it for about a month. A 5 second google search would have saved you 30 days of wasted time. http://www.macromedia.com/cfusion/knowledgebase/index.cfm?id=tn_15512 ___ 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
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
Re: [Flashcoders] PrintJob causes Abort Script error message.
Steven's response was a little unhelpful :) Is this a known Flash bug? It's not a bug. I would suggest that it is: there's no error in the code, and it's not that the Flash movie itself is running slowly, it's purely a result of user interaction. While the print dialogue is displayed, the Flash movie should simply not be running. 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
RE: [Flashcoders] PrintJob causes Abort Script error message.
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
RE: [Flashcoders] PrintJob causes Abort Script error message.
It's not a bug, its poor programming by Macromedia... Fact is, the Flash Player should put the PrintJob process into a separate thread, but it doesn't... My guess is that Macromedia doesn't want to use any more than a single thread in a single Flash Player instance ;-) Lee -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Danny Kodicek Sent: 29 March 2006 12:03 To: Flashcoders mailing list Subject: Re: [Flashcoders] PrintJob causes Abort Script error message. Steven's response was a little unhelpful :) Is this a known Flash bug? It's not a bug. I would suggest that it is: there's no error in the code, and it's not that the Flash movie itself is running slowly, it's purely a result of user interaction. While the print dialogue is displayed, the Flash movie should simply not be running. 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
RE: [Flashcoders] PrintJob causes Abort Script error message.
I would suggest that it is: there's no error in the code, and it's not that the Flash movie itself is running slowly, it's purely a result of user interaction. While the print dialogue is displayed, the Flash movie should simply not be running. PrintJob makes a synchronous call to the OS. Flash ceases to execute code until it receives a response. Unfortunately, this means Flash is hung on a line of code which means Flash is going to throw up an error after 15 seconds because it believes, and rightfully so, that it has code that is unresponsive. It is not a bug. It's the way PrintJob is written - synchronously. ___ 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
Re: [Flashcoders] PrintJob causes Abort Script error message.
On 29 Mar 2006, at 12:07, Steven Sacks wrote: I would suggest that it is: there's no error in the code, and it's not that the Flash movie itself is running slowly, it's purely a result of user interaction. While the print dialogue is displayed, the Flash movie should simply not be running. PrintJob makes a synchronous call to the OS. Flash ceases to execute code until it receives a response. Unfortunately, this means Flash is hung on a line of code which means Flash is going to throw up an error after 15 seconds because it believes, and rightfully so, that it has code that is unresponsive. It is not a bug. It's the way PrintJob is written - synchronously. No, it really is a bug. The bug is that the Flash Player doesn't suppress the timeout notification when a PrintJob is active. It is quite reasonable to expect a user to spend more than 15 seconds configuring their print settings. Since I very much doubt that this was intended behaviour, I would class this as a bug. -- Steve Webster Head of Development Featurecreep Ltd. http://www.featurecreep.com 14 Orchard Street, Bristol, BS1 5EH 0117 905 5047 ___ 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
Re: [Flashcoders] PrintJob causes Abort Script error message.
I would suggest that it is: there's no error in the code, and it's not that the Flash movie itself is running slowly, it's purely a result of user interaction. While the print dialogue is displayed, the Flash movie should simply not be running. PrintJob makes a synchronous call to the OS. Flash ceases to execute code until it receives a response. Unfortunately, this means Flash is hung on a line of code which means Flash is going to throw up an error after 15 seconds because it believes, and rightfully so, that it has code that is unresponsive. It is not a bug. It's the way PrintJob is written - synchronously. Er - and I'd say that's a bug (in Flash, not in the OP's code). The code that checks if a movie is hanging should be looking at number of lines of code executed. While a modal dialogue is up, it shouldn't be being called at all. 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
RE: [Flashcoders] PrintJob causes Abort Script error message.
No need to use flasm here, the SLI Injector will do the same since it´s nothing more than a Tag in the SWF File. http://www.buraks.com/swfsli/ hth -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steven Sacks Sent: Wednesday, March 29, 2006 1:05 PM To: 'Flashcoders mailing list' Subject: RE: [Flashcoders] PrintJob causes Abort Script error message. 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 ___ 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
RE: [Flashcoders] PrintJob causes Abort Script error message.
Either way, the fact is theres not much to be done... And no Flash Player update will help, because most users will still have the buggy version. Lee -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Danny Kodicek Sent: 29 March 2006 12:26 To: Flashcoders mailing list Subject: Re: [Flashcoders] PrintJob causes Abort Script error message. I would suggest that it is: there's no error in the code, and it's not that the Flash movie itself is running slowly, it's purely a result of user interaction. While the print dialogue is displayed, the Flash movie should simply not be running. PrintJob makes a synchronous call to the OS. Flash ceases to execute code until it receives a response. Unfortunately, this means Flash is hung on a line of code which means Flash is going to throw up an error after 15 seconds because it believes, and rightfully so, that it has code that is unresponsive. It is not a bug. It's the way PrintJob is written - synchronously. Er - and I'd say that's a bug (in Flash, not in the OP's code). The code that checks if a movie is hanging should be looking at number of lines of code executed. While a modal dialogue is up, it shouldn't be being called at all. 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
RE: [Flashcoders] PrintJob causes Abort Script error message.
PrintJob works fine in simplistic Flash movies. Try and do anything advanced (such as a stock exchange trading system) and it will cause the alert to appear. That ain't an error with my code! --- On Wed 03/29, Steven Sacks [EMAIL PROTECTED] wrote: From: Steven Sacks [mailto: [EMAIL PROTECTED] To: flashcoders@chattyfig.figleaf.com Date: Wed, 29 Mar 2006 03:34:35 -0800 Subject: RE: [Flashcoders] PrintJob causes Abort Script error message. The modal dialog does not belong to Flash, it belongs to Windows, andspecifically it belongs to the browser window that contains the Flash movie.This being said, I have a Flash app that uses PrintJob and I just testedkeeping my PrintJob dialog open for a full 3 minutes and I did not get analert that Flash was hung.So, it looks like you have some other issue with your movie and PrintJobisn't to blame.-Steven -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Danny Kodicek Sent: Wednesday, March 29, 2006 3:26 AM To: Flashcoders mailing list Subject: Re: [Flashcoders] PrintJob causes Abort Script error message. I would suggest that it is: there's no error in the code, and it's not that the Flash movie itself is running slowly, it's purely a result of user interaction. While the print dialogue is displayed, the Flash movie should simply not be running. PrintJob makes a synchronous call to the OS. Flash ceases to execute code until it receives a response. Unfortunately, this means Flash is hung on a line of code which means Flash is going to throw up an error after 15 seconds because it believes, and rightfully so, that it has code that is unresponsive. It is not a bug. It's the way PrintJob is written - synchronously. Er - and I'd say that's a bug (in Flash, not in the OP's code). The code that checks if a movie is hanging should be looking at number of lines of code executed. While a modal dialogue is up, it shouldn't be being called at all. 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://[EMAIL PROTECTED] change your subscription options or search the archive:http://chattyfig.figleaf.com/mailman/listinfo/flashcodersBrought to you by Fig Leaf SoftwarePremier Authorized Adobe Consulting and Traininghttp://www.figleaf.comhttp://training.figleaf.com ___ 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
RE: [Flashcoders] PrintJob causes Abort Script error message.
Fab, thanks, I'll give it a try. --- On Wed 03/29, =?iso-8859-1?Q?Andr=E9_Goliath?= [EMAIL PROTECTED] wrote: From: =?iso-8859-1?Q?Andr=E9_Goliath?= [mailto: [EMAIL PROTECTED] To: flashcoders@chattyfig.figleaf.com Date: Wed, 29 Mar 2006 13:28:18 +0200 Subject: RE: [Flashcoders] PrintJob causes Abort Script error message. No need to use flasm here, the SLI Injector will do the same since it´snothing more than a Tagin the SWF F ___ 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
RE: [Flashcoders] PrintJob causes Abort Script error message.
And for the record, I am certainly no friend of the PrintJob class. It's poorly written and I've pointed out its numerous flaws in previous posts to this list. Yes, it shouldn't have been coded to work the way it does. The way it works is poorly thought out. But, that doesn't mean that it's a bug because it technically is working exactly as it should. Danny Kodicek...I think I remember you from my Director days, so long ago. ___ 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
RE: [Flashcoders] PrintJob causes Abort Script error message.
PrintJob works fine in simplistic Flash movies. Try and do anything advanced (such as a stock exchange trading system) and it will cause the alert to appear. That ain't an error with my code! Ah ha! So now we get to the bottom of it. PrintJob does not cause Flash to alert about a slow running script. We've established that. You can't say it's PrintJob's fault anymore just because your app is more complicated. If it works in a simple test, it works period. The issue lies somewhere else. Without looking at your code, my best guess is that you are running processes at the same time as a PrintJob starts. What's happening is that you have some script expecting a method to finish running, but the PrintJob starts and, because it's a synchronous call, Flash sits and waits. Unfortunately, you've got some other code trying to run or code that was in the middle of something and because it got locked up while Flash waits on the PrintJob to complete, it thinks Flash is locked up and Flash throws the error. So, yes, it is a problem with your code. You need to halt all processes before your PrintJob starts. Do not use the SLI injector to increase the timeout. That's like injecting painkillers in a broken ankle so you can keep running. Fix your code. -Steven ___ 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
Re: [Flashcoders] PrintJob causes Abort Script error message.
And for the record, I am certainly no friend of the PrintJob class. It's poorly written and I've pointed out its numerous flaws in previous posts to this list. Yes, it shouldn't have been coded to work the way it does. The way it works is poorly thought out. But, that doesn't mean that it's a bug because it technically is working exactly as it should. I think we're in a semantic discussion about what is and isn't a bug here. I agree with Steve W: I can't see that the Flash engineers would have specifically designed it with this behaviour in mind, and the behaviour is not what the function ought to do from a user's perspective, therefore it's a bug. (Otherwise you could argue that *every* program is doing exactly what it was programmed to do, therefore nothing is a bug). I would argue that Flash's 'is it hanging' test should be given a hook that the printJob (or other) classes could talk to, which essentially stops it checking until the function is returned. Anyway, I was under the impression that it counted number of lines of code executed, not time taken. In particular, your discovery that this doesn't occur in a barebones movie would seem to imply that it *is* a bug, because somehow the synchronicity isn't being maintained. 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 ___ 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
RE: [Flashcoders] PrintJob causes Abort Script error message.
Remember, though, that should an unforeseen cercumstance occur in your application that will otherwise throw an error will likely hang the users machine with no typical way for the user to escape except to crash the application completely... Most users don't like that too much :-P Lee -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ron Wheeler Sent: 29 March 2006 15:04 To: Flashcoders mailing list Subject: Re: [Flashcoders] PrintJob causes Abort Script error message. Steven Sacks wrote: 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 I would suggest setting the timeout to 7200 seconds and then test it to see what happens if you leave it sitting over lunch. Please warn us when you are going to do this, since from the tone of the conversation, there is some sense that this will cause the end of civilization as we know it. I suspect that the impact will be considerably less and the users of the application may be able to deal with any repercussions by changing their reaction to a dialogue box - it should not be taken as an invitation to go for a coffee. If Macromedia feels OK about the single threading issue, we have to cut ourselves some slack about dealing with it. It certainly is a cautionary note to designers of new applications that you should consider designing in some way to easily shutdown all of the animation and communication functions while setting up a print job. The effect on a communication link of an extended timeout might be one of the problems that you encounter since the other end might decide that you have died over lunch and cut its end. If you are re-establishing the link (authorization???) on each data transfer, this may not be a problem. Ron Ron ___ 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
RE: [Flashcoders] PrintJob causes Abort Script error message.
Wow, I really should break my sentences up with comma's and fullstops. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Lee McColl-Sylvester Sent: 29 March 2006 15:22 To: Flashcoders mailing list Subject: RE: [Flashcoders] PrintJob causes Abort Script error message. Remember, though, that should an unforeseen cercumstance occur in your application that will otherwise throw an error will likely hang the users machine with no typical way for the user to escape except to crash the application completely... Most users don't like that too much :-P Lee -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ron Wheeler Sent: 29 March 2006 15:04 To: Flashcoders mailing list Subject: Re: [Flashcoders] PrintJob causes Abort Script error message. Steven Sacks wrote: 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 I would suggest setting the timeout to 7200 seconds and then test it to see what happens if you leave it sitting over lunch. Please warn us when you are going to do this, since from the tone of the conversation, there is some sense that this will cause the end of civilization as we know it. I suspect that the impact will be considerably less and the users of the application may be able to deal with any repercussions by changing their reaction to a dialogue box - it should not be taken as an invitation to go for a coffee. If Macromedia feels OK about the single threading issue, we have to cut ourselves some slack about dealing with it. It certainly is a cautionary note to designers of new applications that you should consider designing in some way to easily shutdown all of the animation and communication functions while setting up a print job. The effect on a communication link of an extended timeout might be one of the problems that you encounter since the other end might decide that you have died over lunch and cut its end. If you are re-establishing the link (authorization???) on each data transfer, this may not be a problem. Ron Ron ___ 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
Re: [Flashcoders] PrintJob causes Abort Script error message.
Steven Sacks wrote: Please warn us when you are going to do this, since from the tone of the conversation, there is some sense that this will cause the end of civilization as we know it. Hacking the swf to increase the timeout is not the solution, it's a band-aid on a gunshot wound. Maybe he is only nicked and a band-aid might do the job. It is hard to tell without reading all 50,000 lines of his code. In the real world, sometimes you only need to fix the problem in the current release and can fix the design in the next version. Patches are allowed and many patches do not make it into the next release because the underlying problem goes away with a redesign. It is impossible to tell if his application will blow up after the timeout is increased but it is unlikely that it will cause the rest of us much of a problem. Ron I have over 20 years of programming experience including at assembler level, advanced Java, etc, but thanks for trying to put me in my place :-) Let's say for argument's sake that it is a bug and it is all Macromedia's fault and they won't fix it and life is unfair. That doesn't change the fact that your application needs to work to your client's expectations. You need to find a solution because that's what you're paid to do. You hit the nail on the head here - your application needs to work to your client's expectations; not to ours or not to be perfect. As Danny Kodicek knows coming from a Director background, there were tons of bugs in Director and workarounds had to be figured out to make certain things work. John Dowdell, in his infinite wisdom, got on Direct-L and posted that Director had no bugs, that there was just application behavior that Director developers wished worked differently. At the end of the day, I don't tell my client Sorry, it's a bug and I can't work around it. I figure out how to get it done, and so should you and everyone else who does this for a living. The place I'm trying to put you in is Flash Developer. ;) Noble sentiments but sometimes in the real world you have to tell a client Sorry it is a bug/design artifact in the underlying software and I can not fix it or implement a work-around in the budget that you want. Furthermore, the cost of fixing it exceeds the value to the organization. In my work, I can not just charge clients money with no accountability. They expect me to make reasonable judgements about the value of my activities and not to just spend time because I have an ego-driven need to get a perfect solution. I need to be able to explain my position and to demonstrate how my recommendation is in the client's best interest. I do not always know when to quit but not quiting or not accepting a good enough solution is not a virtue (at least not in the eye of the guy paying for it). Ron ___ 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
