Make composite imageSheet

Solar2D Advanced Graphics
#1

Hi all!

This is a question for Corona staff mostly, I believe…

Would it be possible to load 16 images and composite them into a 4096 x 4096 (or any other size) imageSheet? That would allow me to create a nice “progress bar” loader.

As it stands we can use display.capture to create a displayObject, but unfortunately the imageSheet API uses a filename parameter, not an imageObject. Alternatively, I could save out the imageObject and re-load it for use as the imageSheet, but that would defeat the purpose, since I would be loading all separate graphics, saving them as one file and then loading them again, which would take about three times the loading time!

#2

Hi @thomas6,

Perhaps I don’t understand the benefit you’re wanting to gain. If you’re already loading 16 images, and they exist in texture memory, then why do you want to composite them into an image sheet? Is it specifically so that you can use that image sheet for the Corona progressView widget?

Also, where do these images come from, and why are they separated/individual? Does the user have some kind of control on which “pieces” they use, and which will be composited into the image sheet?

Best regards,

Brent

#3

Other way around, unless I’ve wildly misinterpreted him. Amortizing a big, blocking load operation, and giving some idea of its progress along the way. Presumably, since afterward (or during, if memory is really tight and an incremental method is necessary) “they exist in texture memory”, making a composite will be relatively inexpensive. The sub-images are only a means; the image sheet is the end.

#4

Hi!

Sorry for all the confusion! Yes, the only reason for me to do this is to create a progress bar or ring for my load operation. Any thoughts?

#5

Hi @thomas6,

Perhaps I don’t understand the benefit you’re wanting to gain. If you’re already loading 16 images, and they exist in texture memory, then why do you want to composite them into an image sheet? Is it specifically so that you can use that image sheet for the Corona progressView widget?

Also, where do these images come from, and why are they separated/individual? Does the user have some kind of control on which “pieces” they use, and which will be composited into the image sheet?

Best regards,

Brent

#6

Other way around, unless I’ve wildly misinterpreted him. Amortizing a big, blocking load operation, and giving some idea of its progress along the way. Presumably, since afterward (or during, if memory is really tight and an incremental method is necessary) “they exist in texture memory”, making a composite will be relatively inexpensive. The sub-images are only a means; the image sheet is the end.

#7

Hi!

Sorry for all the confusion! Yes, the only reason for me to do this is to create a progress bar or ring for my load operation. Any thoughts?