I have to agree on this. Bubbling custom-dispatched events is a bad idea when you don't have to do it - you could argue that it breaks encapsulation, and it definitely creates noise and excess work for the VM. I try to only use it to announce "business" events, for example "CreateNewUserEvent", or "SuccessfulLoginEvent" and things like that rather than "UI" events.
-Josh On Thu, Jul 10, 2008 at 7:59 AM, Alex Harui <[EMAIL PROTECTED]> wrote: > It wasn't clear whether your renderer was dispatching the event or the > entire dropdown. Yes, you may need two levels of owner.. A renderer in the > dropdown doesn't have any clue it is working for a combobox and you just > have to wire it up correctly. > > > > Personally, I'm not a fan of using bubbling to pass events. IMHO, bubbling > is designed for cases where you cannot know the relationship (something > internal got clicked, scrolled or added). Everything else should be handled > without bubbling. The CB listens for events from the dropdown already. If > I were doing custom work, any additional event would be dispatched from the > dropdown and listened to from the CB. Lots of folks seem to love bubbling, > but I think it is a bad practice when you already have a defined > relationship. > > > -- "Therefore, send not to know For whom the bell tolls. It tolls for thee." :: Josh 'G-Funk' McDonald :: 0437 221 380 :: [EMAIL PROTECTED]
