alex - look closely at the code in your togglebutton1 callback
set(handles.togglebutton2, 'Value', 1);
togglebutton2_Callback(handles.togglebutton2, eventdata, handles)
x=0;
set(handles.edit1, 'String', x);
You set the string for the button and then call the callback for togglebutton2 which includes a while loop. And so long as the condition of the while loop is true, we will never exit the togglebutton2_Callback function and control will never return to togglebutton1_Callback...which means that x never gets initialized and the edit1 control never gets updated. So you probably want to do this before calling the other function.
I don't understand the purpose of the second toggle button. Why is it necessary if the first toggle button starts the counter? Would the user ever push the second toggle button callback? If absolutely necessary, then you could modify your code to be as follows
function togglebutton1_Callback(hObject, eventdata, handles)
ispushed=get(hObject,'Value');
if ispushed
set(hObject, 'String', 'STOP');
x=0;
set(handles.edit1, 'String', x);
set(handles.togglebutton2, 'Value', 1);
togglebutton2_Callback(handles.togglebutton2, eventdata, handles)
else
set(hObject, 'String', 'START');
set(handles.togglebutton2,'Value',0);
end
The above is similar to what you have shown. Note that in the body of the else we set the Value property to zero for the second toggle button so that we exit from the while loop in its callback.
You may want to reconsider some of this code. Ask yourself if the second toggle button is necessary and how you may just use the first one to control the updates to the edit boxes.
