Error using handle.handle/set Invalid or deleted object.

I'm a beginner in guide and I'm doing Fuzzy Inference System Mamdani where I load (pushbutton2 / reset button) and this error appears.

Error using handle.handle/set
Invalid or deleted object.

Error in tahfidz>pushbutton2_Callback (line 189)
set(handles.edit1,'String','')


Error in gui_mainfcn (line 95)
        feval(varargin{:});

Error in tahfidz (line 42)
    gui_mainfcn(gui_State, varargin{:});

Error in
matlab.graphics.internal.figfile.FigFile/read>@(hObject,eventdata)tahfidz('pushbutton2_Callback',hObject,eventdata,guidata(hObject)) 
Error while evaluating UIControl Callback

and this is my code

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

% Last Modified by GUIDE v2.5 23-Oct-2019 10:43:20

% Begin initialization code - DO NOT EDIT
gui_Singleton = 1;
gui_State = struct('gui_Name',       mfilename, ...
                   'gui_Singleton',  gui_Singleton, ...
                   'gui_OpeningFcn', @tahfidz_OpeningFcn, ...
                   'gui_OutputFcn',  @tahfidz_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 tahfidz is made visible.
function tahfidz_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 tahfidz (see VARARGIN)

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

% Update handles structure
guidata(hObject, handles);

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


% --- Outputs from this function are returned to the command line.
function varargout = tahfidz_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)

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



function edit1_Callback(hObject, eventdata, handles)
% hObject    handle to edit1 (see GCBO)
% eventdata  reserved - to be defined in a future version of MATLAB
% handles    structure with handles and user data (see GUIDATA)

% Hints: get(hObject,'String') returns contents of edit1 as text
%        str2double(get(hObject,'String')) returns contents of edit1 as a double
edit1=str2double(get(hObject,'String'));
handles.edit1=edit1;
guidata(hObject,handles);


% --- Executes during object creation, after setting all properties.
function edit1_CreateFcn(hObject, eventdata, handles)
% hObject    handle to edit1 (see GCBO)
% eventdata  reserved - to be defined in a future version of MATLAB
% handles    empty - handles not created until after all CreateFcns called

% Hint: edit controls usually have a white background on Windows.
%       See ISPC and COMPUTER.
if ispc && isequal(get(hObject,'BackgroundColor'), get(0,'defaultUicontrolBackgroundColor'))
    set(hObject,'BackgroundColor','white');
end



function edit2_Callback(hObject, eventdata, handles)
% hObject    handle to edit2 (see GCBO)
% eventdata  reserved - to be defined in a future version of MATLAB
% handles    structure with handles and user data (see GUIDATA)

% Hints: get(hObject,'String') returns contents of edit2 as text
%        str2double(get(hObject,'String')) returns contents of edit2 as a double
edit2=str2double(get(hObject,'String'));
handles.edit2=edit2;
guidata(hObject,handles);

% --- Executes during object creation, after setting all properties.
function edit2_CreateFcn(hObject, eventdata, handles)
% hObject    handle to edit2 (see GCBO)
% eventdata  reserved - to be defined in a future version of MATLAB
% handles    empty - handles not created until after all CreateFcns called

% Hint: edit controls usually have a white background on Windows.
%       See ISPC and COMPUTER.
if ispc && isequal(get(hObject,'BackgroundColor'), get(0,'defaultUicontrolBackgroundColor'))
    set(hObject,'BackgroundColor','white');
end



function edit3_Callback(hObject, eventdata, handles)
% hObject    handle to edit3 (see GCBO)
% eventdata  reserved - to be defined in a future version of MATLAB
% handles    structure with handles and user data (see GUIDATA)

% Hints: get(hObject,'String') returns contents of edit3 as text
%        str2double(get(hObject,'String')) returns contents of edit3 as a double
edit3=str2double(get(hObject,'String'));
handles.edit3=edit3;
guidata(hObject,handles);

% --- Executes during object creation, after setting all properties.
function edit3_CreateFcn(hObject, eventdata, handles)
% hObject    handle to edit3 (see GCBO)
% eventdata  reserved - to be defined in a future version of MATLAB
% handles    empty - handles not created until after all CreateFcns called

% Hint: edit controls usually have a white background on Windows.
%       See ISPC and COMPUTER.
if ispc && isequal(get(hObject,'BackgroundColor'), get(0,'defaultUicontrolBackgroundColor'))
    set(hObject,'BackgroundColor','white');
end



function edit4_Callback(hObject, eventdata, handles)
% hObject    handle to edit4 (see GCBO)
% eventdata  reserved - to be defined in a future version of MATLAB
% handles    structure with handles and user data (see GUIDATA)

% Hints: get(hObject,'String') returns contents of edit4 as text
%        str2double(get(hObject,'String')) returns contents of edit4 as a double


% --- Executes during object creation, after setting all properties.
function edit4_CreateFcn(hObject, eventdata, handles)
% hObject    handle to edit4 (see GCBO)
% eventdata  reserved - to be defined in a future version of MATLAB
% handles    empty - handles not created until after all CreateFcns called

% Hint: edit controls usually have a white background on Windows.
%       See ISPC and COMPUTER.
if ispc && isequal(get(hObject,'BackgroundColor'), get(0,'defaultUicontrolBackgroundColor'))
    set(hObject,'BackgroundColor','white');
end


% --- Executes on button press in pushbutton1.
function pushbutton1_Callback(hObject, eventdata, handles)
% hObject    handle to pushbutton1 (see GCBO)
% eventdata  reserved - to be defined in a future version of MATLAB
% handles    structure with handles and user data (see GUIDATA)
a=readfis('tahfidz')
out=evalfis([handles.edit1 handles.edit2 handles.edit3],a);
set(handles.edit4,'String',out);

% --- Executes on button press in pushbutton2.
function pushbutton2_Callback(hObject, eventdata, handles)
% hObject    handle to pushbutton2 (see GCBO)
% eventdata  reserved - to be defined in a future version of MATLAB
%handles    structure with handles and user data (see GUIDATA)
set(handles.edit1,'String','')
set(handles.edit2,'String','')
set(handles.edit3,'String','')
set(handles.edit4,'String','')

Answer 1

[Walter Roberson]

In your callback for edit1 you replace the handle with the value extracted from the handle. That is confusing at the very least.

[Arif Fauzan]

hmm...

then what is the solution?

i am truly newbie..

and thank you for your answer

[Walter Roberson]

Remove edit1_Callback and edit2_Callback and edit3_Callback

Change

out=evalfis([handles.edit1 handles.edit2 handles.edit3],a);

to

edit1=str2double(handles.edit1.String);
edit2=str2double(handles.edit2.String);
edit3=str2double(handles.edit3.String);
out=evalfis([edit1, edit2, edit3], a);

[Arif Fauzan]

big thanks for you sir...

that's working....thank you so much

[Novianas Hafidz]

Bang, maksudnya gimana bang? Thanks atas penjelasannya.

[Walter Roberson]

The user had

function edit1_Callback(hObject, eventdata, handles)
% hObject    handle to edit1 (see GCBO)
% eventdata  reserved - to be defined in a future version of MATLAB
% handles    structure with handles and user data (see GUIDATA)
% Hints: get(hObject,'String') returns contents of edit1 as text
%        str2double(get(hObject,'String')) returns contents of edit1 as a double
edit1=str2double(get(hObject,'String'));
handles.edit1=edit1;
guidata(hObject,handles);

However, when you are using GUIDE then in order for GUIDE to have created a function named edit1_Callback then the user must have created a graphics object with the tag "edit1": callback functions are given a name which is the tag of the object, followed underscore, followed by "Callback".

So we know that the user has an object with the tag "edit1". At the time that GUIDE starts the gui, it looks for all of the tags, and for each tag, it creates a field in the handles structure with a field name that is the same as the tag. So graphics object edit1 will result in field handles.edit1 being created. The value that GUIDE puts into the field will be the handle of the graphics object, so handles.edit1 will be set to the handle of the graphics object with the tag edit1.

Now look at the code that the user put into the callback. The callback gets a string and interprets the string as a double. Then it stores the double into handles.edit1 . So afterwards handles.edit1 is the number, instead of being the handle to the graphics object. After you have done this, you can no longer refer to the graphics object, because you replaced the handle with a number!

This is not an absolutely impossible situation to work with, if you know what you are doing, but someone who knows what they are doing would not deliberately make life harder by coding this way.