error while ploting and save

When run show this error even Mapping Toolbox is installed

Warning: Probably because you do not have Mapping Toolbox, getar was performed by an approximative method.

> In getar (line 24)

2nd not save figures

[Walter Roberson]

I cannot seem to find any MATLAB-coded function named getar anywhere ? What software are you running?

[Shaukat]

its simple code extension,but it also not save figures when click save as it shows error

[Shaukat]

My matlab not save the figures and show some errors as below

Error using printopt

Too many input arguments.

Error in matlab.graphics.internal.mlprintjob

Error in printjob (line 22)

pj = matlab.graphics.internal.mlprintjob;

Error in filemenufcn>localExportTypes (line 353)

[a,opt,ext,d,e,output,name]=printtables(printjob(hfig)); %#ok

Error in filemenufcn>localSaveExport (line 306)

typesorig = localExportTypes(hfig);

Error in filemenufcn (line 58)

localSaveExport(hfig, false)

Error while evaluating Menu Callback.

[Shaukat]

Can some guide mefor right person who resolved my simple issue .ie., why not my installed matlab not save figure.?

[Walter Roberson]

Experiment with giving the command

restoredefaultpath; rehash toolboxcache

and then run your code again. If the code starts working then you have a function somewhere on your path (such as a third-party toolbox) that has the same name as a Mathworks function and is interfering with the Mathworks function. If the code does not start working, then there might still be the same problem but with the interfering function being in your current directory.

I notice that the error message does not give a line number within printopt even though that is .m source code, such as at toolbox/local/printopt.m . That hints that you are somehow invoking a different printopt .

The supplied printopt does not itself check the number of input arguments, and ignores its input arguments. It calls upon the functions isempty, message, strcmp, system_dependent, warning (and also ispc but does not supply any parameters to that call). All of those are important internal functions; if you are somehow redefining those then you would have run into a lot of other problems. So I would tend to suspect that the problem would be in a different printopt being invoked.