2023b Compatibility with 2019b code?

I am trying to run code in 2023b that works fine on an old 2019b instance. I know MatLab is meant to be backwards compatible but is there a limitation on how many versions are supported?

I am getting the following error messages:

Warning: In a future release, UI components will not be included in the output. To include UI

components, use the exportapp function.

> In print (line 86)

In FuzzyResponse>cmdOK_Callback (line 1031)

In gui_mainfcn (line 95)

In FuzzyResponse (line 43)

In matlab.graphics.internal.figfile.FigFile/read>@(hObject,eventdata)FuzzyResponse('cmdOK_Callback',hObject,eventdata,guidata(hObject))

In uiwait (line 81)

In FuzzyResponse>FuzzyResponse_OpeningFcn (line 87)

In gui_mainfcn (line 220)

In FuzzyResponse (line 41)

In SessionPlan (line 124)

In Dashboard>cmdOK_Callback (line 143)

In gui_mainfcn (line 95)

In Dashboard (line 42)

In matlab.graphics.internal.figfile.FigFile/read>@(hObject,eventdata)Dashboard('cmdOK_Callback',hObject,eventdata,guidata(hObject))

Unrecognized function or variable 'print2array'.

Error in export_fig (line 334)

[A, tcol] = print2array(fig, magnify, renderer);

Error in AssessmentBoth>cmdContinue_Callback (line 301)

export_fig(completeFileName,'-nocrop') ;

Error in gui_mainfcn (line 95)

feval(varargin{:});

Error in AssessmentBoth (line 42)

gui_mainfcn(gui_State, varargin{:});

Error in matlab.graphics.internal.figfile.FigFile/read>@(hObject,eventdata)AssessmentBoth('cmdContinue_Callback',hObject,eventdata,guidata(hObject))

Error while evaluating UIControl Callback.

Answer 1

[John D'Errico]

Is there a limit? No limit is ever published. The first is a warning, NOT an error message. It is intended to tell you there will be a problem at some point in the future, and that it would be a good idea for you to modify your code as soon as possible to prevent being surprised one day in a new release.

They do strive mightily to insure that MATLAB stays compatible across releases. But sometimes growth requires change. New features sometimes just don't fit inside the old package. Some changes are OS or CPU determined, and are outside their control.

The second message you show is indeed an error message. It is telling you there is some function missing that you have not provided.

which print2array -all

'print2array' not found.

So this is not a function they provide to you. You must have written it and then lost it, or gotten the code from some source that uses a function by that name.

[Walter Roberson]

print2array is part of export_fig https://www.mathworks.com/matlabcentral/fileexchange/23629-export_fig

[Steven Lord]

Note that the error occurs inside export_fig, which is not part of MATLAB but is a File Exchange submission. The Functions tab of that submission lists print2array.

So one possible cause of the error is that you're mixing versions of this File Exchange submission (export_fig.m from a newer version, which uses print2array.m, and the set of helper functions from an older version of that submission which predates the introduction of that helper.)