Thanks Alex specifying a rowHeight fixed the problem. However there's
still an interesting/odd thing in this case which I forgot to mention
in my post. The setter itself executes twice for every row in the
list, and this also seems to be a default behaviour. To be more
specific if
the data
is your renderer complex and using bindings? Try making use of invalidation
approaches. eg, in set data() call invalidateProperties() and override
commitProperties() where you do the actual work. Ely G has a great paper
talking about this approach.
If anything you do invalidates the List, it will re-render everything.
From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On
Behalf Of the_braniak
Sent: Tuesday, May 20, 2008 12:27 AM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Re: Using custom
Hi Douglas,
Thanks for the reply, I'll have a look at this ASAP.
To answer your question, about the complexity of the renderer it doesn
't matter, I tried it with a simple renderer and tests data and the
behaviour is the same. The overidden data setter executes twice. I
don't know if there is a
--- In flexcoders@yahoogroups.com, the_braniak [EMAIL PROTECTED]
wrote:
Hi all,
In my application I am pooling data every 3 seconds. The data goes
into a model which updates a view. I am using a list with a custom
Item renderer. In the custom itemRenderer I am overriding the data
5 matches
Mail list logo