From a high level perspective, scrolling is moving data through fixed itemRenderers, not by actually moving renderers off the visible area of
the screen.
I found this little bit of information hidden in this thread. After trying to extensively use my PageList component in a large application and with a dataProvider that had the potential of providing hundreds of items needing rendering I was noticing a very bad side effect. My application would continue to create a new instance of the itemRenderer for every item in the dataProvider and if the dataProvider was emptied ( ie: arrayCollection.removeAll() ) the itemRenderers would remain.
Back to the drawing board on that one. I hope to post a new PageList component soon as my application is not usable in it’s current state.
has there been any advances with this TileList BUG?
Nope. There is no fix to the bug as it’s just a case of bad design really.