I know this is an old thread, but for those who come across this in the
future, this is a great article that sums up the problem and solutions quite
well:
http://www.adobe.com/devnet/flex/articles/itemrenderers_pt3_02.html
Aaron
On Fri, Jan 8, 2010 at 10:47 PM, Aaron Hardy aaronius...@gmail.com
Thanks for sharing your thoughts and examples. In my case I decided to pass
in a model with a property into the renderers. The model is passed into the
renderer by specifying it as a property value in the renderer class
factory. The model doesn't ever get replaced after that, but the property
Good point. So maybe I have to categorize everything as being data (in
which case it hangs out with the data object) or style (in which case it
would be applied to all the renderers and can be ran through the various
style mechanisms). To be clear, the changes (that aren't data-dependent)
being
Yes, I suppose the line of what is or is not a style can be blurry at
times. In any case, using transient properties inside a VO is what I was
eluding in the first item of things I've thought of, the downside being
that a model/VO of some type is needed in order to keep the renderer
notified of
I think there might be a misunderstanding. If it's a transient property on
the data objects that come through the data provider, I would have to change
the property for all the objects in the data provider to be the same value
since I want all the renderers to change in the same way. For
5 matches
Mail list logo
