Matlab App designer - use 'close all' without deleting GUI

Hi All

A quick one but one I am having issues with. Currently I am developing a GUI which has several quite complex image processing functions within it that are activated via buttons etc within the GUI. The current issue I have is that many of these scripts currnetly use a

close all

command to clear all their handles and created figures upon finishing. The issue I am finding now is that this also closes the GUI window as well which is not what I want!

Is there an alternative way of doing this in which I can close the handles etc within the functions without closing the GUI windown itself. I have tried commenting out the 'close all' statements within the functions but this made them very buggy so I need to find a way of clearing them if at all possible....

Any answers much appreciated!

Answer 1

[Rik]

You can use handles returned on the opening the figure to close them:

f=figure;
%some interaction with the figure
plot(rand(2,10))
%another figure
f(2)=figure;
bar(1:4);

%close the specific figures (works with an array of handles)
close(f)

[dweather]

Thanks for this, it does the job for the figures. I have a more interesting problem now however.

The function in question also reads from and writes to an excel file during it's operation. When I try and run this script as a function within the GUI, it gets halfway through and then returns an error stating that the sheet cannot be written to as it is locked by another process. Sure enough when I check the task manager there is an Excel process hanging open at this point.

However, if I comment out the function/end statements and run the script as a standalone, it runs without error!

Any ideas on this would be welcome as I'm very confused...!

[Rik]

Glad to be of help.

As to your new problem, it might be caused by a number of things. Is your code using an ActiveX server, or the normal xlswrite tool? Does quiting the process (through taks manager) and then running it as function work?

In file IO there shouldn't really be a difference between functions and scripts.

[dweather]

Yes, I was very confused about this too, it's xlswrite and I've used it in other functions called by the GUI without issue.

I've ended up using a !kill at the allifcted part of the script, and that seems to have fixed it (although I appreciate it's a bit of a fudge!).

Thanks for your help though!

Answer 2

[Image Analyst]

See this link