itemRenderers are recycled for better performance. So I'm not sure what you would do, but this is just a heads up.
Thanks for the quick reply Greg.
I'm not limited to loading the images this way. I had just seen something similar and was trying to adapt it. Do you have any ideas on another method or control that would be better suited to loading many large images such as this quicker than loading all of the originals every time?
1 person found this helpful
I would store thumbnails on the server with the images themselves, and just deliver the thumbnails initially.
Then as the user needs the actual images, get them from the server.
Of course this depends on the actual workflows of your app.
I posted 2 examples on item renderers this weekend on my blog, check out the examples: http://blog.wisebisoft.com/2009/05/09/working-with-item-renderers/ As Greg already mentioned, item renderers get recycled so you need to make sure that when you scroll the list then each item renderer is correctly updated.
With best regards,
EDIT: the only difference that you might see in my examples are that I chose to embed the images since they were really small. In your case, you could keep then in an Array and assign each image when needed.