Comments on: No flash events after PrintJob.start()

By: Mike

Mike — Wed, 26 May 2010 19:01:07 +0000

We ran into this exact same issue. We also used a template based system for our reports and would utilize databinding which would cause the templates to sometimes load images. We moved away from templates to rendering every page in advance and making sure all images were fully loaded and then printing. Depending on the number of reports and records they selected it could eat up to a gig of ram (which we found the OS never fully reclaimed even though Flex Builder profiler didn’t indicate any instances hanging around). We now settled on a solution to load all images up before printing (array of Loader objects) and then create images from the binary image data as we move through the template/record combination’s. The good thing about this (even though we should never have had to do it) is we probably will never hit the 15 second timeout on addPage with a print job as all images (or external resources) will be 100% loaded. Hope this helps!

By: derRaab

derRaab — Thu, 10 Sep 2009 08:48:07 +0000

Sorry, I guess there is no solution.

By: Matthew

Matthew — Tue, 08 Sep 2009 20:32:33 +0000

Hello! This is an excellent post. It is good to co-miserate with others having the same problem.

I would like to know if you were able to find a solution to this problem.

1) Avoiding Script-Timeouts
2) Use the flash event model. Specifically, adding pages on EnterFrame and not having the printJob close the spool upon leaving a frame.

Thanks.

Have a nice day.

By: Mike Kayser

Mike Kayser — Fri, 17 Apr 2009 14:42:28 +0000

You could create and print a smaller number of pages at a time. That would solve crashing and timeout issues, not much I could recommend about quality.

By: Tom Goethals

Tom Goethals — Tue, 13 Jan 2009 10:06:29 +0000

We have the exact same problem and no fix.