problems deploying a GUI to windows

Hi. I'm having several problems deploying a GUI to Windows.

I'm running R2010b under Window 7 (32b). I wrote a GUI which works fine under MATLAB.

1st problem: The build process works fine. The packaging process works fine SOMETIMES, but some other time (unpredictable to me) give the following error:

zip I/O error: Permission denied zip error: Could not create output file (C:/Users/guido/Documents/MATLAB/Mie_pkg.exe)

Why? And why not regularly? At the beginning I was creating the pkg file in the Desktop, and it was always giving this problem. Now, in the MATLAB directory created by MATLAB installation, I get it right MOST of the time, but not always! I'm getting crazy with this ...

2nd problem: even when the packaging step works fine, I cannot try my application. It' always complaining that "could not find version 7.14 of the MCR", whether I installed (letting the package do it for me or running the MCRInstaller directly). What's wrong?

I kept the log file of the build (long file) and packaging (short file) if useful.

3rd problem: this is more from an unexperienced user of MATLAB ... under certain rare conditions my GUI may give an error. Running it under MATLAB this is not a problem, but would it be a problem in a standalone application? would it make the application crash? and if yes, is there a way to redirect error messages, say, to a file and avoid crashing?

Thanks for your help.

Answer 1

[Sean de Wolski]

• Are you using a supported compiler? R2012b Supported compilers
• Use:

dbstop if error

Then run the GUI until you get the error, it'll stop and show you what's going on. Fix it!

Answer 2

[Guido]

Thank Sean.

I don't know if i'm using a supported compiler. I just start the deploytool from Start | Matlab compiler..

I understand your point. Usually I know what the error is. For example, I let the user choose a data file using uigetfile but if the user cancels the selection window, I get an error. I would like to let the user go on with no problem (and not managing all possible behaviours within the code, I have a limited time).

Thanks.

[Sean de Wolski]

use a try/catch block

doc try