How to Run a .fig file separately without using of it's .m file

Today i coded a UI program.. This is the code of it :-

function varargout = han(varargin)
% HAN M-file for han.fig
%      HAN, by itself, creates a new HAN or raises the existing
%      singleton*.
%
%      H = HAN returns the handle to a new HAN or the handle to
%      the existing singleton*.
%
%      HAN('CALLBACK',hObject,eventData,handles,...) calls the local
%      function named CALLBACK in HAN.M with the given input arguments.
%
%      HAN('Property','Value',...) creates a new HAN or raises the
%      existing singleton*.  Starting from the left, property value pairs are
%      applied to the GUI before han_OpeningFcn gets called.  An
%      unrecognized property name or invalid value makes property application
%      stop.  All inputs are passed to han_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 han

% Last Modified by GUIDE v2.5 22-Jul-2014 15:27:35

% Begin initialization code - DO NOT EDIT

gui_Singleton = 1;
gui_State = struct('gui_Name',       mfilename, ...
                 'gui_Singleton',  gui_Singleton, ...
                 'gui_OpeningFcn', @han_OpeningFcn, ...
                 'gui_OutputFcn',  @han_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

% --- Executes just before han is made visible.
function han_OpeningFcn(hObject, eventdata, handles, varargin)
% This function has no output args, see OutputFcn.
% hObject    handle to figure
% eventdata  reserved - to be defined in a future version of MATLAB
% handles    structure with handles and user data (see GUIDATA)
% varargin   command line arguments to han (see VARARGIN)

% Choose default command line output for han
handles.output = hObject;

% Update handles structure
guidata(hObject, handles);

% UIWAIT makes han wait for user response (see UIRESUME)
% uiwait(handles.figure1);

% --- Outputs from this function are returned to the command line.
function varargout = han_OutputFcn(hObject, eventdata, handles) 
% varargout  cell array for returning output args (see VARARGOUT);
% hObject    handle to figure
% eventdata  reserved - to be defined in a future version of MATLAB
% handles    structure with handles and user data (see GUIDATA)
handles.value=0;
guidata(hObject,handles);
% get(handles.push);

% Get default command line output from handles structure
varargout{1} = handles.output;

% --- Executes on button press in push.
function push_Callback(hObject, eventdata, handles)
% hObject    handle to push (see GCBO)
% eventdata  reserved - to be defined in a future version of MATLAB
% handles    structure with handles and user data (see GUIDATA)
handles.value=handles.value+1;
a=handles.value;
guidata(hObject,handles);
set(handles.text1,'String',num2str(a));
if(a==25)
  msgbox('Limit exceed','Sorry','warn');
close(handles.figure1);
end

it is running perfectly, but my problem is when i try to run it's .fig file it showing error:-

_ _ * __??? Attempt to reference field of non-structure array.

Error in ==> han>push_Callback at 87
handles.value=handles.value+1;

Error in ==> gui_mainfcn at 96
      feval(varargin{:});

Error in ==> han at 44
  gui_mainfcn(gui_State, varargin{:});

Error in ==> @(hObject,eventdata)han('push_Callback',hObject,eventdata,guidata(hObject))

??? Error while evaluating uicontrol Callback__ * _ _

where should i declare handle.value please help me,,,.....

[Arun Mathew Iype]

Hi Could you give a sample command you use to execute this function? Arun

Answer 1

[Geoff Hayes]

The GUI figure file is not meant to be executed. Double-clicking on the MyGui.fig file will just cause the figure to open and appear as if it is a fully functional GUI, but without any of the (internal) initializations that would normally occur...and so errors will occur.

The GUI is meant to be run from the command line simply as

 >> MyGui

[Arun Bisoyi]

Thanks Hayes

Answer 2

[Joseph Cheng]

I don't understand what you mean by running the fig by itself without the m file as the fig contains the UI graphics (and some hidden programming stuff) and the m file contains the callback. you'll need to use both. You should initialize handles.value in the

% --- Executes just before han is made visible.
function han_OpeningFcn(hObject, eventdata, handles, varargin)
% This function has no output args, see OutputFcn.
% hObject    handle to figure
% eventdata  reserved - to be defined in a future version of MATLAB
% handles    structure with handles and user data (see GUIDATA)
% varargin   command line arguments to han (see VARARGIN)

% Choose default command line output for han
handles.output = hObject;
handles.value = 0; %initialize handles.value here.
% Update handles structure
guidata(hObject, handles);

What you have now doesn't initialize the handles.value to any value. So in your pushbutton callback there is no value for handles.value to add 1 to. So by initializing handles.value at the start before things are made visible should be the best place to initialize it.

[Arun Bisoyi]

Thank you Joseph

purpose behind this question was:-

if someone want to give privilege to the .m file, so that no one can see the content of .m file.. and how can i do it.

[Joseph Cheng]

I answered that and also saw at the very bottom of the question you also ask where to declare the handles.value.

[Joseph Cheng]

To answer your purpose if that was the initial concern and not that + the handles declaration, then use pcode to change the mfile into a pfile which is encrypted and no one can see the content of the mfile. also what i think you mean to say is that "if someone wanted to restrict privilege to the mfile." as giving privilege would give someone access to it. Restrict would mean to deny access to the content.