By passing in "TriggeringManager", you essentially let an event bubble up from an eventManger.  The triggering manager must be passed in by the caller.  Example:

```javascript
view = Ember.View.extend({
  click: function(){
    console.log("View was clicked");
  },
  eventManager: Ember.Object.create({
    click: function(){
      view.$().trigger('click',this);
    }
  });
})
```
So, when the view is clicked upon, the event manager's click function is the one that is triggered.  The event manager click function re-triggers the event, and passes in itself as the "triggeringManager".  This causes the event to bubble up to the click function on the view itself.  

I don't think this is necessarily handled the best way it could be, but wanted to keep this functionality in place so it would not break if anyone was using it.  

Also, as an eventManger is simply an Ember,Object, it would be difficult to determine "triggeringManager" is an EventManager, or some other kind of Ember Object that we might actually want passed through?

Does that clear things up a bit? Any ideas on how we could clean up the re-dispatching logic? Maybe we setup a "re-dispatch" event specifically for handling these scenarios?