Hi Mike, About the memory issues and images how did you get it to release the memory in Flex?
I noticed that when we try to load images to an mx:Image object in a loop
containing this:
// imgObj already defined as an mxml Image object
for (var i:int = 0; i < 5; i++) {
imgObj.source = null; // This doesn't clear the memory... but the docs say
it should...
imgObj.source = ImageFileArray[i].path;
}
The memory taken by each image is not freed.... can you shed some light as
to why it doesn't release it?
Thanks!
-Daniel
On Jan 22, 2008 1:51 PM, Greg Hess <[EMAIL PROTECTED]> wrote:
> Thanks, much appreciated!
>
>
>
> -Greg
>
>
>
> *From:* [email protected] [mailto:[EMAIL PROTECTED] *On
> Behalf Of *Mike Krotscheck
> *Sent:* Tuesday, January 22, 2008 10:27 AM
> *To:* [email protected]
> *Subject:* RE: [flexcoders] Photo print service
>
>
>
> Sortof? When developing HP Print Studio (http://www.hp.com/printstudio) we
> ran into this very same issue, but instead of photos we had multiple high
> resolution template assets that were only loaded when a printjob was
> requested. Given our use cases (most users don't have duplex printers) we
> didn't actually have to do multi-page printing so it's not quite what you're
> looking for, but the implementation might be similar.
>
>
>
> Basically what you want to create is a temporary sandbox object that
> exists on the displaylist (so content is rendered) but doesn't actually show
> anything (height and width = 0). Within that object you compose your print
> pages, paying special attention to keep track of how many images are
> currently loading using event listeners- in particular the load complete
> event. Once everything's signaled that it's ready you print, and in the
> meantime put up a progress bar popup of some kind.
>
>
>
> You might also be able to do delayed page instantiation, that is: create a
> page, wait for it to finish, add it to the print job, destroy it, move to
> the next page. This will give you better memory management overall (I think)
> since you don't have to load your entire photo album into ram before
> printing.
>
>
>
> Also, be careful about your image sizes: Images in memory suck up a LOT of
> ram.
>
>
>
> *Michael Krotscheck*
>
> Senior Developer
>
>
>
> *RESOURCE INTERACTIVE*
>
> www.resource.com
>
> [EMAIL PROTECTED]
>
>
>
>
> ------------------------------
>
> *From:* [email protected] [mailto:[EMAIL PROTECTED] *On
> Behalf Of *Greg Hess
> *Sent:* Tuesday, January 22, 2008 9:56 AM
> *To:* [email protected]
> *Subject:* [flexcoders] Photo print service
>
> Hi All,
>
> I have a requirement to build a photo print service in Flex. The EU will
> view a gallery of image thumbnails (TileList) and have the option to print
> one photo or the entire contents of the gallery. Photo print options would
> be fit to page, 5x7, 8x10 ect…
>
> Searching the web, viewing the docs and examples using the FlexPrintJob
> from my understanding I can print images but they must be loaded (drawn) in
> flex prior, is this true?
>
> For a single photo print job this is fine as I can have the print page
> display the selected image size prior to sending the print job. However, I
> also want to allow the EU to select an entire photo folder and print the
> contents all to say 5x7, is this possible?
>
> Does anyone know of any examples or sample code?
>
> Any comments much appreciated.
>
> Thanks,
>
>
> Greg
>
>
> We support privacy and confidentiality. Please delete this email if it was
> received in error.
>
> *What's new ::*
> Capitalize on the social web* *| The Open Brand, a new book by Kelly
> Mooney and Dr. Nita Rollins, available March 2008 |* www.theopenbrand.com*
>
>
>
--
-------------
e: [EMAIL PROTECTED]
w: http://DanielTse.com/
-------------
<<image001.gif>>
