Marc what is your problem?
Is that a way of saying it wasn't clear?
Anyways, I did hit the 'save' button on my thread BEFORE entering my question... I just updated the contents of the main topic to include my questions.
But just in case, here they are again:
So the end result of all this is that, when I first run the app, all my data in my SLOTS arrays are doubled.... meaning they all appear twice on the screen (ie. I've got one slots array with 3 items in it, well it shows up with 6 on screen).
Second issue is that whenever I resize the screen (ie. Restore/Maximise), a new set of items get added to the grid, but this time, not doubled. So if I restore and maximize my screen, I end up with 4 times the initial number of items in my ArrayCollection...
Any ideas why this might be happening?
If you need more details let me know.
So as you can see, my problem is that I am seeing double all my entries the first time my app starts, and then every resize ads another set of data in my datagrid column...
I see, a small suggestion why instead of doing a repeater you use a function and a loop. The problem must be the fact that on resize the Flash Player re-renders your app, and calls over and over the repeater.
So you're suggesting I use a function with a loop instead of my repeater?
Yes. I think there lies your problem and you have almost all done in a
Ok so I replaced the repeater with a for-loop in my creationComplete event of my itemrenderer.
this seems to work fine
All items are generated ONLY ONCE and don't repeat on resize/restore/maximize of the browser.
Thanks a lot Michael!
I do have another question though... if you notice in the item renderer code above, there is a VBox that I display with no data in my Tile Container... the reason why its there is that if I don't put it in, all my rendered sub-items (called OtherItemMXML in the code above) are stacked one over the other... do you have any idea why this might happen? Or should I just open an alternate threat since its a totally different question?
I'm a bit lazy today could you upload your code to test it, or send it to mabs_corp [@] hotmail.com
That happens because you're using UIComponent, that's a pretty top level class, so it doesn't have many properties that controls that inherit from it have, if you for instance use a Box instead of UIComponent, you won't need the VBox at the end.