It may be caused by Container not implementing IDropInListItemRenderer or
IListItemRenderer. You really don't want to be extending Container for item
renderers if you can avoid it, I believe it's a big performance penalty.
-Josh
2009/1/21 tonyjobrien <ya...@indigointernet.co.uk>
> --- In flexcoders@yahoogroups.com, "sunild999999" <sunilbd...@...> wrote:
> >
> > I got your example to work by removing the Canvas tags from this
> snippet:
> >
> > <mx:itemRenderer>
> > <mx:Component>
> > <mx:Canvas>
> > <mx:Label text="{data.label}" blendMode="layer"/>
> > </mx:Canvas>
> > </mx:Component>
> > </mx:itemRenderer>
> >
> >
> > Sunil
> >
>
> Perhaps I should have been clearer in my original description. The
> issue seems to be related to the use of containers as custom
> renderers. While I admit that in this case, removal of the container
> solves the issue, this is just a simple case to demonstrate the issue.
> In my real life case, my item renderers are much more complicated,
> containing many sub-components, hence the use of containers.
>
>
> ------------------------------------
>
> --
> Flexcoders Mailing List
> FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
> Alternative FAQ location:
> https://share.acrobat.com/adc/document.do?docid=942dbdc8-e469-446f-b4cf-1e62079f6847
> Search Archives:
> http://www.mail-archive.com/flexcoders%40yahoogroups.comYahoo! Groups
> Links
>
>
>
>
--
"Therefore, send not to know For whom the bell tolls. It tolls for thee."
Like the cut of my jib? Check out my Flex blog!
:: Josh 'G-Funk' McDonald
:: 0437 221 380 :: j...@gfunk007.com
:: http://flex.joshmcdonald.info/
:: http://twitter.com/sophistifunk
