Code covered by the BSD License  

Highlights from
Using RTW and Compiler

from Using RTW and Compiler by Tan Chin Luh
Stand alone application example using rapid simulation file.

guide302(varargin)
function varargout = guide302(varargin)
% GUIDE302 Application M-file for guide302.fig
%    FIG = GUIDE302 launch guide302 GUI.
%    GUIDE302('callback_name', ...) invoke the named callback.

% Last Modified by GUIDE v2.0 25-Feb-2002 16:11:30

if nargin == 0  % 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 nargout > 0
		varargout{1} = fig;
	end

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

	try
		if (nargout)
			[varargout{1:nargout}] = feval(varargin{:}); % FEVAL switchyard
		else
			feval(varargin{:}); % FEVAL switchyard
		end
	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= pbPlot_Callback(h, eventdata, handles, varargin)
a=get(handles.lbInput,'string');
b=get(handles.lbInput,'value');
c=strcat(a(b),'data.mat');
d=get(handles.editGain,'String');
e=get(handles.sldTime,'Value');
e=round(e);
e=num2str(e);
e=[' ',e];
load guide302para
myrtp.parameters.values = str2num(d);
save guide302para2.mat myrtp
line1=strcat('!guide302model -f guide302data.mat=',char(c),' -p',' guide302para2.mat',' -s',e);
eval(line1);
load guide302model;
plot(rt_tout,rt_yout);

% --------------------------------------------------------------------
function varargout = figure1_CreateFcn(h, eventdata, handles, varargin)
t=[0:0.1:100];
u=sin(t);
tu=[t;u];
save sindata.mat tu

u=square(t);
tu=[t;u];
save squaredata.mat tu

u=sawtooth(t);
tu=[t;u];
save sawtoothdata.mat tu

% --------------------------------------------------------------------
function varargout = sldTime_Callback(h, eventdata, handles, varargin)
e=get(handles.sldTime,'Value');
e=round(e);
set(handles.text1,'string',num2str(e));

Contact us at files@mathworks.com