Error in appdesigner number of arguments

MATLAB version: 2022b.

When creating a simple app with just one single push button, and assigning a callback MATLAB automatically creates a function for the pushbutton:

function ButtonPushed(app, event)

But later, in the properties of the pushbutton, it creates thre arguments for the callback function:

app.Button.ButtonPushedFcn = createCallbackFcn(app, @ButtonPushed, true);

If I try to run this app, I get continuously the error:

Error using uibutton

Incorrect number of input arguments.

Error in temp1 (line 46)

createComponents(app)

How can I avoid that inconsitency? MATLAB does it automatically for me and I cannot change it because it is not in the editable area.

I have attached a screenshot.

Can someone please help me out?

Answer 1

[Matt J]

There's nothing wrong with the code. I suspect you have defined your own version of uibutton() somewhere shadowing the builtin function? Execute the following and report the output to us,

which -all uibutton

[Miguel A.]

This is the output of that command:

U:\Folder\matlab\scripts\uibutton\uibutton.m

C:\Program Files\MATLAB\R2022b\toolbox\matlab\uicomponents\uicomponents\uibutton.m % Shadowed

Thank you for pointing this out. I removed/renamed the first uibutton.m file and now each application is working. Probably there was some conflict in the uibutton.m function used by MATLAB. Unfortunately, MATLAB did not pointed in that direction with its error message. This thread is thus solved.

[Stephen23]

"May be there is nothing wrong with the code, but MATLAB is unable to run such a simple application."

Because you have created a file named UIBUTTON which shadows the inbuilt function.

"It produces the same error each time: a difference in the number of arguments for the Pushbutton."

Because you have created a file named UIBUTTON which shadows the inbuilt function.

"This is the output of that command"

U:\Folder\matlab\scripts\uibutton\uibutton.m % !!!!!!!! DELETE or RENAME !!!!!!!!!!!

[Miguel A.]

Thank you so much. Problem is solved. Issue seems to have raised when ICT related migration of user profiles internally at my institution took place and I had to redefine again my path.