Suppose I have a input box that requires an entry greater than zero before attempting to load a file.
function test_Callback(hObject, eventdata, handles)
test = str2double(get(hObject, 'String'));
if isnan(test)
set(hObject, 'String', 0);
errordlg('Input must be a number','Error');
end
handles.backup.test= test; guidata(hObject,handles)
function loaddata_Callback(hObject, eventdata, handles)
test_Callback(hObject, eventdata, handles)
[filename, pathname, Index] = ...
uigetfile({'*.txt';},['Select the File to load'],...
'\\MyDocuments\User');
This prompts the error "'Input must be a number','Error'' and allows the user to open and search for this file. What am I doing wrong?
No products are associated with this question.
You need to put this
test = str2double(get(hObject, 'String'));
if isnan(test)
set(hObject, 'String', 0);
errordlg('Input must be a number','Error');
endin a loop and not leave the loop until you have a legal value from the user.
BTW: I think it is a good habit to close functions with "end".
.
A detail: change
set(hObject, 'String', 0);
to
set(hObject, 'String', '0' );
.
An example according to my originally answer. This code gives the user ten chances to enter a correct value.
function test_Callback(hObject, eventdata, handles)
for ii = 1 : 10
test = str2double(get(hObject, 'String'));
if isnan(test)
set(hObject, 'String', 0);
errordlg('Input must be a number','Error');
elseif gt(test,1)
handles.backup.test = test;
guidata(hObject,handles);
break
elseif gt(1,test)
set(hObject, 'String', '0');
errordlg('Input must be greater than 0','Error');
end
end
end
@Per, I agree with using "end"s as a best practice but it is true that in GUIDE it creates all of the functions without them so adding end to one means you have to add it to all which takes time and makes it harder to add/change functionality.
Of course my best practice is to just write the GUI as a class or function anyway..
if is_ok
[filename, pathname, Index] = ...
uigetfile({'*.txt';},['Select the File to load'],...
'\\MyDocuments\User');
else
some_dialog('enter a positive integer and try again')
end
6 Comments
Direct link to this comment:
http://www.mathworks.com/matlabcentral/answers/63530#comment_130032
You ask for too much guessing. Please describe in some detail
Direct link to this comment:
http://www.mathworks.com/matlabcentral/answers/63530#comment_130068
Current behavior in a possible use case (I have not tested):
Is this the way your code works?
(1) doc says: Note A modal dialog box prevents the user from interacting with other windows before responding. To block MATLAB program execution as well, use the uiwait function.
Direct link to this comment:
http://www.mathworks.com/matlabcentral/answers/63530#comment_130189
Edited version of your comment:
user clicks [loaddata]
if gui finds e.g. a character in [test] gui presents [errordlg] elseif gui finds 0 gui presents [errordlg] endgui presents [uigetfile]
user picks a file in [uigetfile]
So basically how the code should work is described. But the problem is that when I add the elseif statement to test_callback after isnan.
Direct link to this comment:
http://www.mathworks.com/matlabcentral/answers/63530#comment_130797
I insist that it is a good thing to first specify how the code should work. And it is easier to read code that is properly formatted; use [Smart Intent] in the editor. See code in my answer.
Direct link to this comment:
http://www.mathworks.com/matlabcentral/answers/63530#comment_130871
Yes, but what does the code that I added to my answer do?
Direct link to this comment:
http://www.mathworks.com/matlabcentral/answers/63530#comment_131078
Change
to