Uh, well, he was sort of right. TileList did not recycle nearly as often as other lists in Flex 2 and now it does.
________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Tracy Spratt Sent: Wednesday, April 02, 2008 10:42 AM To: [email protected] Subject: RE: [flexcoders] Item renderer behavior change in Flex3 ?? "...Flex2, the "creationComplete" handler was always executed in renderer when the TileList data provider..." No, it wasn't. You were getting lucky some other way. itemRenderer behavior has not changed significantly between 2 and 3. All updates to a renderer must be triggered by the set data() override and, ideally the invalidation system. Tracy ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Robert Csiki Sent: Wednesday, April 02, 2008 1:09 PM To: [email protected] Subject: [flexcoders] Item renderer behavior change in Flex3 ?? Hello Code that used to work with Flex2 does not work right with Flex3. I have a TileList with a custom item renderer. The renderer has view states, it also has handler for "creationComplete". With Flex2, the "creationComplete" handler was always executed in renderer when the TileList data provider changes. In Flex3, it is executed just once ant that's it (i.e. when the data provider changes the list gets refreshed but my handler does not get executed). Does Flex3 use some sort of pooling for renderer instances? Also as I said, my renderer has view states. Handlers for enterState, exitState etc are only executed once, for the initial data provider. I see all this as beeing a grave backwards compatibility issue. Comments? Thanks, Robert
