Environmental Engineering Reference
In-Depth Information
Let's have a look on the M-file. It starts with the following commands:
function
varargout = transport(varargin)
% TRANSPORT
M-file
for transport.fig
% TRANSPORT, by itself, creates a new TRANSPORT or raises the
% existing singleton*.
%
% H = TRANSPORT returns the handle to a new TRANSPORT or the
% handle to the existing singleton*.
%
% TRANSPORT('CALLBACK',hObject,eventData,handles,...) calls
% the local function named CALLBACK in TRANSPORT.M with the
given input arguments.
% TRANSPORT('Property','Value',...) creates a new TRANSPORT or
% raises the existing singleton*. Starting from the left,
% property value pairs are applied to the GUI before
% transport_OpeningFunction gets called. Anunrecognized
% property name or invalid value makes property application
% stop. All inputs are passed to transport_OpeningFcn via
% varargin. *See GUI Options on GUIDE's Tools menu. Choose
% "GUI allows only one instance to run (singleton)".
%
% See also: GUIDE, GUIDATA, GUIHANDLES
% Edit the above text to modify the response to help transport
% Last Modified by GUIDE v2.5 22-Sep-2006 16:50:52
% Begin initialization code - DO NOT EDIT
gui_Singleton = 1;
gui_State = struct('gui_Name', mfilename, ...
'gui_Singleton', gui_Singleton, ...
'gui_OpeningFcn', @transport_OpeningFcn, ...
'gui_OutputFcn', @transport_OutputFcn, ...
'gui_LayoutFcn', [] , ...
'gui_Callback', []);
if
nargin && ischar(varargin{1})
gui_State.gui_Callback = str2func(varargin{1});
end
if
nargout
[varargout{1:nargout}] = gui_mainfcn(gui_State, varargin{:});
else
gui_mainfcn(gui_State, varargin{:});
end
% End initialization code - DO NOT EDIT
As already outlined above, a function with the same name (here:
'transport'
)is
created.
varargin
and
varargout
are lists of input- and output parameters. What
follows is a list of comments and the initialization of the entire structure. As the
details are relevant for the specialist only, we skip any explanation but pinpoint to
the very last comment of this part of the program. It tells the user that all statements
above concern initialization and may under no circumstances be edited.
After the initialization part several subfunctions follow, starting with the open-
ing function
function
transport_OpeningFcn(hObject, eventdata, handles, varargin)
