You can extend it, that is probably the simplest. You would probably just override set data() or createChildren().
In my case, I did not want the icon, but needed some other controls conditionally, so I just esentially copied the code I needed. I found that dynamically creating the controls in set data or updateDisplayList was too slow, and ended up instantiating my additional controls just once in createChildren(), then toggling their visibility, location and content in set data() If you do this, be sure to change all the references to ListItemRenderer to match your own component file name. I also had to take out some other arcane framework stuff. And since the support classes are no longer in the same folder as the renderer, you will need to import those classes. Tracy ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of David Ham Sent: Friday, September 07, 2007 3:22 PM To: [email protected] Subject: [flexcoders] Re: Unwanted scrollbars on my List itemRenderer--measure() help? Tracy, I tried creating an MXML component based on ListItemRenderer, and it said a strange thing: I got a compiler error that said it couldn't resolve <mx:ListItemRenderer> to a component implementation. Do I need to create a new AS class that extends ListItemRenderer, and implement its various interfaces? Also, can I still use custom stuff like Texts and Linkbuttons in it? Thanks so much, OK DAH
