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
