User`s guide

Limitations and Restrictions
1-21
in callback strings.) The Compiler processes any function listed in a
%#function pragma.
For example, the call to the
change_colormap function in the sample
application,
my_test, illustrates this problem. To make sure the Compiler
processes the
change_colormap M-file, list the function name in the
%#function pragma:
function my_test()
% Graphics library callback test application
%#function change_colormap
peaks;
p_btn = uicontrol(gcf,...
'style', 'pushbutton',...
'Position',[10 10 133 25 ],...
'String', 'Make Black & White',...
'CallBack','change_colormap');
Note Instead of using the %#function pragma, you can specify the name of
the missing M-file on the Compiler command line.
Finding Missing Functions in an M-File
To find functions in your application that may need to be listed in a %#function
pragma, search your M-file source code for text strings specified as callback
strings or as arguments to the
feval, fminbnd, fminsearch, funm, and fzero
functions or any ODE solvers.
To find text strings used as callback strings, search for the characters
Callback or fcn in your M-file. This will find all the
Callback properties
defined by Handle Graphics
®
objects, such as uicontrol and uimenu. In
addition, this will find the properties of figures and axes that end in
Fcn, such
as
CloseRequestFcn, that also support callbacks.