在用GUIDE 中怎么样在 axes 区域显示图片啊？它的代码如何编写？如图


生成的M文件如下，其中“axes(handles.axes1); ”那几句是我写的，想用来显示图片，可是 不行啊。那命令在MATLAB7.0中是可以的，不知道怎么搞了。请大家帮忙！谢谢了

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

% Last Modified by GUIDE v2.0 28-Jul-2006 12:45:28

if nargin == 0 % LAUNCH GUI

fig = openfig(mfilename,'reuse');

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

axes(handles.axes1);
[x,map]=imread('dankuozhang.bmp');

imshow(x);
axis off;

axes(handles.axes2);
[x,map]=imread('dankuozhangcharu.bmp');

imshow(x);
axis off;

axes(handles.axes3);
[x,map]=imread('kuozhangchuanlian.bmp');

imshow(x);
axis off;

% 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 = radiobutton1_Callback(h, eventdata, handles, varargin)

set(findobj(gcf,'Tag','radiobutton2'),'Value',0);
set(findobj(gcf,'Tag','radiobutton3'),'Value',0);

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

set(findobj(gcf,'Tag','radiobutton1'),'Value',0);
set(findobj(gcf,'Tag','radiobutton3'),'Value',0);

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

set(findobj(gcf,'Tag','radiobutton1'),'Value',0);
set(findobj(gcf,'Tag','radiobutton2'),'Value',0);

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

if get(handles.radiobutton1,'value')==1;
gykz;close (xuanze);
elseif get(handles.radiobutton2,'value')==1;
ncg;close (xuanze);
elseif get(handles.radiobutton3,'value')==1;
gz;close (xuanze);

end

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

close;