You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please see Matlab error message below for details.
My interpretation: Example models are installed somewhere in "C:\Programm files", where I do not have write access. When selecting one of those examples in the GUI, it (tries) to write the ouput into the folder where the XML is, not where Matlab currently is. Latter pointing to a potential solution. Alternatively, offer option to specify output folder, or maybe only generate .m and let the user afterwards safe it manually. Work-around:
I would consider this low prio as there is an easy workaround (that worked for me): copy file to a folder where you have write access. And when choosing your own XML this is likely located in a folder with write access anyway.
---- from Matlab prompt ---
generateMatlabCodeForXML
Error using fclose
Invalid file identifier. Use fopen to generate a valid file identifier.
Error in generateMatlabCodeForXML>writeToFile (line 758)
fclose(fid);
Error in generateMatlabCodeForXML>OK_pushbutton_Callback (line 97)
writeToFile(handles);
Error in gui_mainfcn (line 95)
feval(varargin{:});
Error in generateMatlabCodeForXML (line 45)
gui_mainfcn(gui_State, varargin{:});
Error in
matlab.graphics.internal.figfile.FigFile/read>@(hObject,eventdata)generateMatlabCodeForXML('OK_pushbutton_Callback',hObject,eventdata,guidata(hObject))
Error while evaluating UIControl Callback
The text was updated successfully, but these errors were encountered:
Please see Matlab error message below for details.
My interpretation: Example models are installed somewhere in "C:\Programm files", where I do not have write access. When selecting one of those examples in the GUI, it (tries) to write the ouput into the folder where the XML is, not where Matlab currently is. Latter pointing to a potential solution. Alternatively, offer option to specify output folder, or maybe only generate .m and let the user afterwards safe it manually. Work-around:
I would consider this low prio as there is an easy workaround (that worked for me): copy file to a folder where you have write access. And when choosing your own XML this is likely located in a folder with write access anyway.
---- from Matlab prompt ---
Error in generateMatlabCodeForXML>writeToFile (line 758)
fclose(fid);
Error in generateMatlabCodeForXML>OK_pushbutton_Callback (line 97)
writeToFile(handles);
Error in gui_mainfcn (line 95)
feval(varargin{:});
Error in generateMatlabCodeForXML (line 45)
gui_mainfcn(gui_State, varargin{:});
Error in
matlab.graphics.internal.figfile.FigFile/read>@(hObject,eventdata)generateMatlabCodeForXML('OK_pushbutton_Callback',hObject,eventdata,guidata(hObject))
Error while evaluating UIControl Callback
The text was updated successfully, but these errors were encountered: