Re: Error Messages of Compiled Programs
- From: "Steven Lord" <slord@xxxxxxxxxxxxx>
- Date: Thu, 4 Dec 2008 09:52:51 -0500
"Geoffrey" <geoffrey.bourque@xxxxxxxxxx> wrote in message
news:gh8qh6$jtq$1@xxxxxxxxxxxxxxxxxxxxx
I'm currently developing a GUI based software that will in the end be
compiled with the MATLAB Compiler. The problem is, I have a lot of
information about error messages currently being sent to the command
window using fprintf commands. When I finish the final development, I want
a user to be able to access whatever normally would have shown up on the
command window.
The problem is that certain callbacks call other functions that have been
developed - and every function could write to it at a different time. Has
someone run into this problem before, or could suggest ideas about how to
go about creating a 'log' file for this situation?
I'd probably create a function, something like logErrorMessage below, and
call that instead of using ERROR directly:
function logErrorMessage(msgid, msgtxt)
if isdeployed
% Write to the log file -- perhaps store the fid for the log file in a
persistent variable?
else
% Write the message to the screen -- perhaps by calling ERROR directly
end
You could also create a logWarningMessage as well.
--
Steve Lord
slord@xxxxxxxxxxxxx
.
- Follow-Ups:
- Re: Error Messages of Compiled Programs
- From: Geoffrey
- Re: Error Messages of Compiled Programs
- References:
- Error Messages of Compiled Programs
- From: Geoffrey
- Error Messages of Compiled Programs
- Prev by Date: Re: RS232 and Escorts 3136A
- Next by Date: Re: Matlab problem, please help!!!
- Previous by thread: Error Messages of Compiled Programs
- Next by thread: Re: Error Messages of Compiled Programs
- Index(es):
Relevant Pages
|