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
