MATLAB Runtime Server

Organizing Files and Managing Startup Tasks

This example places its own MATLAB files in toolbox\mydir during the entire development, compilation, and testing process. If you change any application file while exploring this example, use rehash toolboxreset to register the changes.

The Visual Basic files for this example can be in any convenient location.

The Startup Function

The example matlabrt.m file, which the section MATLAB Startup Functions instructed you to install in the toolbox\local directory, is appropriate for this application because it:

• Does not display anything in the command window
• Does not set the global error behavior for the application. MATLAB errors do not suspend execution of a MATLAB runtime engine application; that is, the error behavior of the application is fixed in 'continue' mode.
• Sets the warning level to off
• Invokes pathdefrt (not pathdef)
• Does not launch other MATLAB application functions because the front end of this application ultimately launches myapp.p

Creating the Path Definition Function

The example pathdefrt.m file that you installed in toolbox\local uses paths relative to the MATLAB root directory. Each distinct directory that contains a function used in this application is included on the runtime path.

Notice that the list of directories in the example pathdefrt.m matches the list of (non-private, non-class) directories in the output of the depdir function.

• cleanp; % Remove all .p files from path
  p = depdir('myapp')
  p = ['$toolbox/local:',...
       '$toolbox/mydir:',...
       '$toolbox/matlab/graphics:',...
       '$toolbox/matlab/uitools:',...
       '$toolbox/matlab/graph3d:',...
       '$toolbox/matlab/general:',...
       '$toolbox/matlab/lang:',...
       '$toolbox/matlab/specfun:',...
       '$toolbox/matlab/strfun:',...
       '$toolbox/matlab/ops:',...
       '$toolbox/matlab/datafun:',...
       '$toolbox/matlab/elmat:'];
  

Adapting the Design for Runtime Execution

Compiling the Application