Re: ItemRenderer Render Order

HaHaha!!! Thanks for the suggestions Javier, your input has been invaluable. I am not the most elegant of coders, so I tend to like neanderthal approaches ;) Homo sapiens may be a little too enlightened for me. I saw all of the information about the priority groups that you mention with the

Re: ItemRenderer Render Order

Nice going! Erik On Oct 12, 2017, at 4:12 PM, bilbosax wrote: I initially tried Erik's solution to use a contentCache with queueing enabled, and set maxActiveRequests to 3, but I still got the same results - one of the first three images was always the last to render.

Re: ItemRenderer Render Order

I initially tried Erik's solution to use a contentCache with queueing enabled, and set maxActiveRequests to 3, but I still got the same results - one of the first three images was always the last to render. So I finally took a more neanderthal approach and have two url ArrayCollections. The

Re: ItemRenderer Render Order

Thanks for the ideas Javier, they are all excellent! I will try some of them out this afternoon and post my results! -- Sent from: http://apache-flex-users.246.n4.nabble.com/

Re: ItemRenderer Render Order

Another few options: 1. Set the dataprovider to only the first 3 entries 2. Wait for complete rendering 3. Set the dataprovider to the whole list of entries and caching will do its job Or just set items 4-99 to not visible, and then turn them back on when items 1-3 finish loading. (you could

Re: ItemRenderer Render Order

There are probably other options as well. You could overlay the list with a single image and have the server concatenate the images into a single long image and send that up. Then under the covers, you bring the individual images into the cache and display them in item renderers. It is more

Re: ItemRenderer Render Order

Thanks for the replies Erik and Alex. When I get back to my computer tomorrow, I will give your suggestions a try and see how it works out. This is a realestate app where property images are displayed when a property is clicked on, so caching beforehand really isn't an option. But I am interested

Re: ItemRenderer Render Order

Here's another idea. It's logical to assume if using non-virtual List, that when the dataProvider is assigned to an ArrayCollection that the collection order (natural, or ordered if you set a Sort in an extended collection) is also the order the ItemRenderers will indeed start rendering in the

Re: ItemRenderer Render Order

Despite the fact that a non-virtual List or DataGroup will attempt to render all ItemRenderer instances by iterating the dataProvider in some sequential order, the speed at which the images appear is only influenced very little by the order the instances are rendered. This is because as each

Re: ItemRenderer Render Order

I don't know enough about the layers of the internet to answer your question, but a network monitor can help show why things are happening the way you describe them, and then you will have more data to use to form a solution/workaround. Right now, all we have is speculation. Think of it this

Re: ItemRenderer Render Order

Hey Bilbosax, I don't see how that setting will help. For best look and feel, I suggest you let the ItemRenderer do it's job which will render the visible ones first but use ContentCache so that the images are loaded only once, so scrolling will be pretty good. That said, you might consider

Re: ItemRenderer Render Order

Well, the player uses deferred rendering, so if you send 20 requests for images and only 10 come back in the next frame interval, those 10 will be rendered all at once and you won't know which of those 10 came back first. Flex item renderers, like all Flex components, use invalidation/validation,

ItemRenderer Render Order

I am writing a mobile app and there is a horizontal list at the bottom of the app that the user can horizontally scroll through a row of photos. I have a custom itemrenderer in the list to just upload and display photos based on a url value. There will never be more than 24 photos, so I thought