> 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.
If I wanted to, I could write a simple movie that causes a timeout popup to appear 15 seconds after I start a PrintJob. It doesn't need to be a complicated stock trading application to cause the behavior Grime is experiencing, and therefore it's a solvable problem. Bottom line here is this: "Is this a known Flash bug?" It's a known Flash limitation. "Is there a workaround?" Yes. But apparently, he's not interested in doing it. I call it as I see it and it's lazy and irresponsible to claim you're not going to fix something because you think your host app should work differently than it does. If you don't like working within the confines of Flash being single-threaded and PrintJob being a synchronous call to the system, then learn C++ and free yourself. Otherwise, step up and do the job you're paid to do - Flash development. I mean, c'mon. It's ok to whine about stuff like this, but at the end of the day you need to make it work because that's what your client is paying you to do. _______________________________________________ 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
