Hi Tracy,
On Mon, Jul 7, 2008 at 6:55 PM, Tracy Spratt [EMAIL PROTECTED] wrote:
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.
Thanks. Yep, that's what
Of Tom McNeer
Sent: Tuesday, July 08, 2008 9:10 AM
To: flexcoders@yahoogroups.com
Subject: Re: [flexcoders] Re: Item renderers cause processor to max out
Hi Tracy,
On Mon, Jul 7, 2008 at 6:55 PM, Tracy Spratt [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Well then, you could use setItemAt
Hi Tracy,
On Tue, Jul 8, 2008 at 2:42 PM, Tracy Spratt [EMAIL PROTECTED] wrote:
You understand that labelFunction is usually used instead of an
itemrenderer? If all you are doing is building and displaying a delimited
list of values, itemRenderer is overkill.
Yep. I understand. I
Hi Tom,
What are you doing with this event in set data?
dispatchEvent(new FlexEvent(FlexEvent.DATA_CHANGE));
It's a loop.
-TH
--- In flexcoders@yahoogroups.com, Tom McNeer [EMAIL PROTECTED] wrote:
Hi,
I began asking about this problem last week and Alex Harui tried to
help me.
But I did
Hi Tim,
Thanks for the reply.
On Mon, Jul 7, 2008 at 10:54 AM, Tim Hoff [EMAIL PROTECTED] wrote:
What are you doing with this event in set data?
dispatchEvent(new FlexEvent(FlexEvent.DATA_CHANGE));
It's a loop.
You're absolutely correct, of course. Unfortunately, my error was
Ok, that makes sense. One other thing that might be contributing is:
updateComplete=setGridHeight(event)
You might want to try:
valueCommit=setGridHeight(event)
instead. Good luck Tom,
-TH
--- In flexcoders@yahoogroups.com, Tom McNeer [EMAIL PROTECTED] wrote:
Hi Tim,
Thanks for the
Hi Tim,
Thanks again for your help. But ...
On Mon, Jul 7, 2008 at 12:03 PM, Tim Hoff [EMAIL PROTECTED] wrote:
Ok, that makes sense. One other thing that might be contributing is:
updateComplete=setGridHeight(event)
You might want to try:
valueCommit=setGridHeight(event)
I
PROTECTED] On
Behalf Of Tim Hoff
Sent: Monday, July 07, 2008 12:04 PM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Re: Item renderers cause processor to max out
Ok, that makes sense. One other thing that might be contributing is:
updateComplete=setGridHeight(event)
You might want to try
--- In flexcoders@yahoogroups.com, Tom McNeer [EMAIL PROTECTED] wrote:
Hi Tim,
Thanks again for your help. But ...
On Mon, Jul 7, 2008 at 12:03 PM, Tim Hoff [EMAIL PROTECTED] wrote:
Ok, that makes sense. One other thing that might be
contributing is:
To both Tracy and Amy,
Thanks a lot for your advice.
Tracy, I'm pretty new to Flex, so I need to ask you for a little
clarification:
On Mon, Jul 7, 2008 at 1:22 PM, Tracy Spratt [EMAIL PROTECTED] wrote:
If you **use the dataProvider API** to update the item, it will cause the
labelFunction
To: flexcoders@yahoogroups.com
Subject: Re: [flexcoders] Re: Item renderers cause processor to max out
To both Tracy and Amy,
Thanks a lot for your advice.
Tracy, I'm pretty new to Flex, so I need to ask you for a little
clarification:
On Mon, Jul 7, 2008 at 1:22 PM, Tracy Spratt [EMAIL PROTECTED
Tracy,
On Mon, Jul 7, 2008 at 3:56 PM, Tracy Spratt [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
@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of Tom McNeer
Sent: Monday, July 07, 2008 3:58 PM
To: flexcoders@yahoogroups.com
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
13 matches
Mail list logo
