modaldlg(varargin)

function answer = modaldlg(varargin)
error(nargchk(0,4,nargin)) %function takes 0, 1, or 4 arguments
% MODALDLG Application M-file for modaldlg.fig
%    FIG = MODALDLG launch modaldlg GUI.
%    MODALDLG('callback_name', ...) invoke the named callback.

% Last Modified by GUIDE v2.0 11-Jul-2002 06:06:10

if nargin == 0 | isnumeric(varargin{1}) % LAUNCH GUI

	fig = openfig(mfilename,'reuse');

	% Use system color scheme for figure:
	set(fig,'Color',get(0,'defaultUicontrolBackgroundColor'));

	% Generate a structure of handles to pass to callbacks, and store it. 
	handles = guihandles(fig);
	guidata(fig, handles);
    
    if nargin == 1
        pos_size=get(fig,'Position');
        pos=varargin{1};
        if length(pos) ~= 2
            error('Input argument must be a 2-element vector')
        end
        new_pos = [pos(1) pos(2) pos_size(3) pos_size(4)];
        set(fig, 'Position', new_pos,'Visible','on')
    end

	% Wait for callbacks to run and window to be dismissed:
	uiwait(fig);
    
    if ~ishandle(fig)
        answer='cancel';
    else
        handles=guidata(fig);
        answer=handles.answer;
        delete(fig);
    end
    

	%if nargout > 0
	%	varargout{1} = fig;
    %end

elseif ischar(varargin{1}) % INVOKE NAMED SUBFUNCTION OR CALLBACK

	try
		[varargout{1:nargout}] = feval(varargin{:}); % FEVAL switchyard
	catch
		disp(lasterr);
	end

end


%| ABOUT CALLBACKS:
%| GUIDE automatically appends subfunction prototypes to this file, and 
%| sets objects' callback properties to call them through the FEVAL 
%| switchyard above. This comment describes that mechanism.
%|
%| Each callback subfunction declaration has the following form:
%| <SUBFUNCTION_NAME>(H, EVENTDATA, HANDLES, VARARGIN)
%|
%| The subfunction name is composed using the object's Tag and the 
%| callback type separated by '_', e.g. 'slider2_Callback',
%| 'figure1_CloseRequestFcn', 'axis1_ButtondownFcn'.
%|
%| H is the callback object's handle (obtained using GCBO).
%|
%| EVENTDATA is empty, but reserved for future use.
%|
%| HANDLES is a structure containing handles of components in GUI using
%| tags as fieldnames, e.g. handles.figure1, handles.slider2. This
%| structure is created at GUI startup using GUIHANDLES and stored in
%| the figure's application data using GUIDATA. A copy of the structure
%| is passed to each callback.  You can store additional information in
%| this structure at GUI startup, and you can change the structure
%| during callbacks.  Call guidata(h, handles) after changing your
%| copy to replace the stored original so that subsequent callbacks see
%| the updates. Type "help guihandles" and "help guidata" for more
%| information.
%|
%| VARARGIN contains any extra arguments you have passed to the
%| callback. Specify the extra arguments by editing the callback
%| property in the inspector. By default, GUIDE sets the property to:
%| <MFILENAME>('<SUBFUNCTION_NAME>', gcbo, [], guidata(gcbo))
%| Add any extra arguments after the last argument, before the final
%| closing parenthesis.



% --------------------------------------------------------------------
function varargout = psbYes_Callback(h, eventdata, handles, varargin)
handles.answer='yes';
guidata(h,handles);
uiresume(handles.fgrExit);

% --------------------------------------------------------------------
function varargout = psbNo_Callback(h, eventdata, handles, varargin)
handles.answer='no';
guidata(h,handles);
uiresume(handles.fgrExit);

% --------------------------------------------------------------------
function varargout = fgrExit_CloseRequestFcn(h, eventdata, handles, varargin)
psbNo_Callback(h, eventdata, handles)