MATLAB: Guidance on Closing a “GUIDE” Gui

closedeleteMATLABuiresume

Hello!

I have been trying to cleanly exit a GUIDE gui, and am a bit confused as to the proper sequence. The OpeningFcn is straighforward, but I don't know about a couple of things:

If you have to close the gui right away (like a security check put in the OpeningFcn isn't met), how do you exit? return()? or call the close function? The close has a modal dialog to see if you want to close, but we don't want to do that if security doesn't pass.
What is the proper sequence to (a) close any open windows that have been created during the session and (b) if you have called uiwait, when do you do the delete(handles.figure1) and the uiresume(handles.figure1)? Or other proper close functions?

Thanks.

Doug

Best Answer

I would recommend putting any checks in a function that itself opens the GUI then you simply don't even attempt to open the GUI if the checks fail. I have been caught out myself with bailing out on a GUI in the OpeningFcn and ending up with a ghost GUI that is in some hidden state.

closereq

should do the job though to close the window although not if you have put things in the CloseRequest function that you do not want to happen in this case.

As far as closing windows that have been opened during a session goes it is entirely down to your application really. As far as I know Matlab does not allow figures to be parented by other figures so I programmed a GUI Manager class that deals with launching GUIs and closes them all down automatically when the manager is deleted (which happens when the 'parent' window closes). Generally though you can just close them yourself in the DeleteFcn or CloseRequestFcn of your main window.

If you call uiwait with a figure handle you don't need an explicit uiresume so long as the figure is closed at some point as this will cause it to resume anyway. You can do a uiresume explicitly though to pair up with a uiwait that was not given a figure handle. Then you can delete the figure whenever you deem appropriate.

Related Solutions

MATLAB: Function open/close for GUI

OpeningFcn

is called on GUI creation and

CloseRequestFcn

is called when the GUI closes, but you have to explicitly add this in GUIDE by right-clicking on the figure in GUIDE and choosing the callback. Then you can put code in it.

DeleteFcn

is also called when the window closes. I forget the differences between this and CloseRequestFcn now, but off the top of my head the CloseRequestFcn should delete the gui (which will call DeleteFcn) otherwise it will not get deleted.

MATLAB: Pass GUI information to another GUI depending on a condition

I don't usually use GUIDE, so forgive me if I explain something that GUIDE takes care of automatically.

You'll probably want the GUI2 to be shown in a modal window. This will prevent the user from accessing GUI1 while GUID2 is running. Basically it treats GUI2 as a dialog-box:

% Put this in your GUIDE OpeningFcn
set(hObject, 'WindowStyle', 'modal');

To freeze execution until GUI2 is closed (or until you tell execution to continue), put this line at the end of the GUI2's OpeningFcn:

% Wait until uiresume is called or figure is closed
uiwait(hObject);

At the end of submit_Callback, you'll want to call uiresume to start executing your code again:

% Let GUIDE resmue execution
uiresume(ancestor(hObject, 'figure'));

Before GUIDE finishes, running your code, it calls OutputFcn to set the your GUI's outputs. You'll want to assign you're output file names here.

% Assign file names to GUIDE output (in OutputFcn)
% (I'm not sure how your file names are stored so I put in a plcae holder)
varargout{1} = file_names;

Be sure to delete GUI2's figure at the end of it's OutputFcn (this will allow your other window to receive focus again):

delete(hObject);

In GUI1, you'll want to have a call like:

file_names = GUI2();

This will start up the GUIDE function for GUI2. On startup, GUIDE will call GUI2's OpengingFcn, which will pause execution until you either close GUI2's window or until uiresume is called in the submit_Callback.

Once execution is resumed, GUIDE will call OutputFcn to set the output values for GUI2. These will then get stored in file_names when control returns to GUI1.

Hope that helps.

Best Answer

Related Solutions

MATLAB: Function open/close for GUI

MATLAB: Pass GUI information to another GUI depending on a condition

Related Question