Yes, you should deal with listData in commitProperties or later. That's why it is only one level of hairy.
________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Tracy Spratt Sent: Friday, September 07, 2007 3:08 PM To: [email protected] Subject: RE: [flexcoders] Re: Unwanted scrollbars on my List itemRenderer--measure() help? "listData is available when ... commitProperties runs" and commitProperties runs after set data(), yes? So if a renderer needs to use listData, it should do that work in commitProperties. Right? That clears up some questions I had about ListItemRenderer. That's 0.2 orders of magnitude less hairy. Tracy ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Alex Harui Sent: Friday, September 07, 2007 5:52 PM To: [email protected] Subject: RE: [flexcoders] Re: Unwanted scrollbars on my List itemRenderer--measure() help? The "rules" are: listData is set for you and should never be modified by the renderer. listData is available when the dataChange event fires or commitProperties runs explicitWidth should be set so use that to your advantage. Is there any way you can know by the url of the image what its height will be? ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of David Ham Sent: Friday, September 07, 2007 2:43 PM To: [email protected] Subject: [flexcoders] Re: Unwanted scrollbars on my List itemRenderer--measure() help? > It should only be one level of hairy, not three... LOL. Sorry, I wax hyperbolic late in the day, when the caffeine has jacked me up and Flex has dragged me behind its car for a ways. I'll dig around in measure() and see what I can do. Do I need to worry about setting listData when I subclass ListItemRenderer? I am getting null object reference errors around it... OK DAH
