Windows Stand Alone GUI Problems (Basic)

Windows Stand Alone GUI Problems (Basic)

Post by cabreg » Sat, 27 Jun 2009 02:08:01

Hi all,

I have a Matlab GUI when executed has good functionality. The program can be though of a calculator and plotter of sorts. When ran, it expects users to pick from a list box, enter values in edit boxes, and generates plots. I would like to make this a sstandalone windows application.

I have gone through

After I go through the deploytool and I get a successful compile message at the end of compliation. however, when I execute the .exe is distr folder I get the matlab bug sound ---'donk'.

No messages. I used mbuild -setup to and the compiler is Microsoft Visual C++ 2008 in C:\Program Files\Microsoft Visual Studio 9.0

What can i do to trouble shoot this problem / solve it?

I am compiling with visual

Windows Stand Alone GUI Problems (Basic)

Post by cabreg » Sat, 27 Jun 2009 22:18:01



Windows Stand Alone GUI Problems (Basic)

Post by Nedeli » Wed, 04 Nov 2009 00:52:02

Hi, I have exactly the same problem.
I can see that the post is quite old, but still have you found a solution.
Thank you.

Windows Stand Alone GUI Problems (Basic)

Post by ImageAnaly » Wed, 04 Nov 2009 01:38:27

Run it from the operating system's command window rather than double
clicking on the icon. It usually goes bonk and then the command
window disappears but if you do Start/Run/Cmd and then change
directory to the folder, and then type in your exe's name then when it
crashes, it should leave the error message in the command console
window and not close it.

In my experience it's most likely due to you trying to access a file
or folder that doesn't exist on your target machine. That's why you
need to do tons of error checking and validation. Use exist() before
trying to open andy file or change directory. Plus use try/catch in
every function and try to fix any potential problems in the catch, for
example set the folder to cd instead of leaving it as null. Sometimes
you'll get the horrible "Failed to decrypt file" error - always tricky
to fix.

Another tip is to try running the "Tools/Show Dependency Report" on
your file before you compile it. And make absolutely sure that you
have included all files that are needed during run time: mat files,
splash images, sample data files, documentation, etc. This is where
using the exist() function before accessing them becomes key.