[4.1.0B3] Component render, afterrender, beforerender handlers in controller.Control

[slemmon]

I found that in [B3] component render, afterrender, and beforerender (I didn't test others, yet) events will fire fine if I set up a listeners config in my class definition or in an instance of the component, but my app's controller's control method would no longer see the events.

I discovered that if I put something in the listeners config on the class definition that the controller would see the event.

*abstract from controller.control()

, 'mygrid': {
    beforerender: function () { console.log('grid afterrender event fired from the controller') }
    , afterrender: function () { console.log('grid afterrender event fired from the controller') }
    , render: function () { console.log('grid render event fired from the controller') }
}

By itself the above code works in B2, but not in B3.

If in mygrid's definition I do the following the above code will fire from the controller (*with afterrender commented out below it won't fire the afterrender event in the controller, but the other two fire - uncomment and all three fire).

, listeners: {
    beforerender: Ext.emptyFn
    , render: Ext.emptyFn
    , afterrender: Ext.emptyFn
}

[LesJ]

See this

[slemmon]

I see. Thx.

[dongryphon]

These are different issues. The link above is specifically about the return value of fireEvent. This is a bug in how the MVC EventBus does not get along with the hasListeners optimization.

Thanks for the report! I'm going to move this to the bugs forum and link a ticket.

[oklymenko]

I see that this bug has just been marked as fixed.

We noticed that in beta-3 the destroy event is not captured by the controller either. The workaround of defining a Ext.emptyFn listener on the component does not seem to help with this particular event.

Does this fix address the destroy event as well as beforerender/render/afterrender?

Thanks.