Oops, yeah, I remember that now.
Well then, you could use setItemAt(), which would do the job, or use itemUpdated(). Or is it updateItem()... anyway, that will refresh the UI, including running the labelFunction. Tracy ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Tom McNeer Sent: Monday, July 07, 2008 3:58 PM To: [email protected] Subject: Re: [flexcoders] Re: Item renderers cause processor to max out Tracy, On Mon, Jul 7, 2008 at 3:56 PM, Tracy Spratt <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > wrote: Do not operate on the underlying Array. Use the ArrayCollection API, specifically addItem(). No refreshing is necessary. But the problem is that I'm not adding an item to the ArrayCollection. I'm adding an item (option) to an Array within an item in the ArrayCollection. The ArrayCollection contains Products. Within each Product is an optionArray. So when I'm adding to the optionArray, the Collection is not aware of a change. And I can't make the optionArray an AC on its own, because of VO mapping issues with server objects. That's why I was suggesting a refresh(), or perhaps an updateItem(). Am I missing something? -- Thanks, Tom Tom McNeer MediumCool http://www.mediumcool.com <http://www.mediumcool.com> 1735 Johnson Road NE Atlanta, GA 30306 404.589.0560
