Put a break point in your event handler. Look at the callstack tab and see what if it is different.
________________________________ From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of tchredeemed Sent: Friday, April 18, 2008 11:04 AM To: flexcoders@yahoogroups.com Subject: [flexcoders] Re: <mx:List> itemRenderer catching event twice im not good with eclipse, can you explain to me your thought process and how i would view the call stack in debug mode (assuming i break inside of the handler, or is that incorrect) --- In flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com> , "Alex Harui" <[EMAIL PROTECTED]> wrote: > > Hard to say. You could be listening twice, dispatching twice or both. > The debugger should let you step out of the handler which should put you > at the dispatchEvent call and show you the call stack so you can see > what is going on. FDB is good at showing instance #'s so you can know > if the event is the same object or another object. > > > > ________________________________ > > From: flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com> [mailto:flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com> ] On > Behalf Of tchredeemed > Sent: Friday, April 18, 2008 10:22 AM > To: flexcoders@yahoogroups.com <mailto:flexcoders%40yahoogroups.com> > Subject: [flexcoders] <mx:List> itemRenderer catching event twice > > > > I have a List. > > the list uses an itemRenderer > > the itemRenderer loads in another component dynamically depending on > data.type > > the components that are loaded in listen for specified events > > why is it that it is catching the event twice, when it is only > dispatched once? > > It is listening on a singletonEnforced class, and it is not a bubbling > event. > > Is this because of the itemRenderer? Is this a stupid mistake that I am > making? >
