Ok, thanks. I can't remember why I even started doing this in the first place - honestly. I do remember having problems with dispatching an event in one particular circumstance, so I did this and didn't look back. Bad habits die hard I guess. Thanks for the response :)
On Thu, Oct 10, 2013 at 9:24 AM, Jeffry Houser <jef...@dot-com-it.com>wrote: > On 10/10/2013 11:14 AM, Thomas Wright wrote: > >> Second - is there a better way to handle this, or is this legit? >> > > From an encapsulation perspective, the renderer shouldn't know its > parents. > I always recommend dispatching an event, that bubbles from the renderer > and then handling it in the component that contains the list. > > In terms of memory management; I'm not sure though. With your approach > you are creating a dependency on the list itemRenderer to its parent two > levels up. > By using events that bubble, you are not creating that dependency. > > -- > Jeffry Houser > Technical Entrepreneur > http://www.jeffryhouser.com > 203-379-0773 > > -- *Thomas Wright* Software Engineer Extension: 1054 Office: [801] 464.4600 Corporate Division twri...@yesco.com
