Success! Looks like we've fixed this one. According to our records the fix was applied for
DSGNR-6337
in
a recent build.
-
Sencha Premium Member
What happened to to the Ext.button.Button button, e, eOpts args for controller
I upgraded from Architect 3.0.4 to 3.1.x and now when I ask the architect to create the event handler for the button click, it doesn't add the (button, e, eOpts) arguments like it did in 3.0.4. Can someone explain how to fix this?
-
Denis -
Just went through creating a controller action for a button's click event.
Architect generated this:
Code:
onMybuttonClick: function(button, e, eOpts) {
}
Can you give us the steps you are taking to assign the controller action?
-
Sencha Premium Member
1. I created the button in one of panels that created in architect.
2. selected the button in the IDE, and clicked on event bindings,
3. selected 'click' in the drop down.
4. selected the created event handler function.
5. right mouse clicked and and selected convert to controller action.
6. selected the controller I wanted.
It created the handler function in the controller, but it did not add the (button, e, eOpts) parameters. I had to select the function in the controller and add the parameters in the Config.BasicFunction.params for the add.
This works, but I didn't have to do that before in release 3.0.4.
-
Thanks, I moved this to the bug forum.
The bug only occurs when converting an existing event binding to a controller action. If you create the controller action directly it will create the proper method signature.