Error API for Application Development

Those of us developing graphical applications in MATLAB do not want our users to be exposed to the internals of our work. Unfortunately, the built-in "error" function prefixes to the error message the name of the function which threw that error, which is unlikely to be of any interest to the user and serves only to confuse. This is particularly true when using the MATLAB Compiler to create applications for use by people with no knowledge of MATLAB.
The API supplied here provides a wrapper for the "error" function which stores the error message without that extra line, so that it can be retrieved later and shown to the user.

To use this functionality, replace calls to "error" with identical calls to "xError", e.g.:

error('MyApplication:MyErrorIdentifier','This operation did not work because %s',reason);

becomes:

xError('MyApplication:MyErrorIdentifier','This operation did not work because %s',reason);

Also, replace calls to "lasterr" or "lasterror" with "xLastErr" or "xLastError" respectively, creating e.g.

function my_uicallback
try
my_function_name;
catch
errordlg(xLastErr,'My Application','modal');
end

The error message shown to the user is then simply (e.g.):

This operation did not work because the file was not found

instead of:

Error using ==> my_function_name
This operation did not work because the file was not found

For debugging purposes, the error message and the call stack at the point when it was thrown are stored in a log file in the user's preference directory. The log can also be used to store status messages from the application. See function xLog.

If the last error was thrown using "error" instead of "xError", "xLastError" detects this. This ensures that the wrong error message is never shown, and means that errors thrown by built-in functions (or the interpreter) can be logged too.

Use the buttons in the supplied demo function "xDemo" to see the difference.