I couldn't reproduce the specific error regarding the non-cell object; I got a cell array returned; would seem to need the case in context to reproduce. Then again, I don't have Simulink so I can't simulate calling the function that way.
However, your code isn't testing for the empty return nor that the values are acceptable and the result in the cell array will be a char() string, NOT a numeric value even if the user does "the right thing". This is a tough way to get the input and control what the user does --
...
answer = inputdlg(prompt,dlgtitle,dims);
if isempty(answer)
answer=1; % the default answer???
else
answer=str2double(answer{:}); % convert to number
if isfinite(answer) % could convert the string to a number
if ismember(answer,[0 1]) % make sure either 0,1
else
answer=1; % default if not???
end
end
end
switch answer
case 1
...
is a start but not even close to being fully robust to check alternatives --
I suggest something more like
yn = questdlg('Yes or No?','Input','Yes','No','Yes');
if matches(yn,'Yes')
y=100;
else
y=10;
end
at least controls the possible return values to something you know is one of the two possible button answers although there is also again the possibility the user closes the dialog without selecting either in which case the return is the empty char() vector...the above ignores that possibility and lumps it in with a 'No'
You'll have to decide how to handle all the possibilities but I'd definitely stay away from freeform user input here...they could type in Hamlet's soliloguy in the box for you to parse above -- not that that's likely, but there's no way to limit just typing errors...
