|
Thanks Steve.
For the 'command window', I was referring to is the console window used in
standalone mcc application to display errors thrown or maybe take user input
through input() command, NOT the standard MATLAB prompt where
I can enter arbirary commands. (I just noticed that there's a
'commandwindow'
command in the documentation link you just showed).
"Steven_Lord" <slord@mathworks.com> wrote in message
news:jbane5$cjr$1@newscl01ah.mathworks.com...
>
>
> "Hoi Wong" <wonghoi.ee@gmailNOSPAM.com> wrote in message
> news:jb9bj1$44k$1@newscl01ah.mathworks.com...
>> I'm looking to optionally (depending on program input) open a command
>> window for Matlab compiled DLL (like a standalone application) to aid
>> debugging. Is there a easy way to do so?
>
> No. The Command Window is specifically called out in the documentation for
> MATLAB Compiler as functionality that cannot be included in applications
> created by MATLAB Compiler.
>
> http://www.mathworks.com/products/compiler/compiler_support.html
>
> Nor can the command-line debugging functions be included in such an
> application.
>
> http://www.mathworks.com/help/toolbox/compiler/br2cqa0-20.html
>
> Assuming that the problem does not exist in the application when run in
> MATLAB itself, only in the application generated by MATLAB Compiler, you
> could display text in a figure window to aid in debugging or write
> diagnostic information to a log file using the low-level file I/O
> functionality like FOPEN, FPRINTF, and FCLOSE. If the problem exists when
> you run either the application generated by MATLAB Compiler or the
> application inside MATLAB, you can of course use the debugging
> capabilities of MATLAB to debug the problem.
>
> --
> Steve Lord
> slord@mathworks.com
> To contact Technical Support use the Contact Us link on
> http://www.mathworks.com
|