'uiresume(f5)' is a bad definition of a callback. Callbacks defines as strings are supported for a backward compatibility with Matlab 5.3 from the year 1999. They are evaluated in the base workspace (the command window), such that the variable "f5" must exist there and have the correct value. Use a function handle instead:
uicontrol('style','pushbutton','string','ok', ...
'callback', @ResumeCallback);
...
function ResumeCallback(hObject, EventData)
FigH = ancestor(hObject, 'figure');
uiresume(FigH);
end
Instead of stopping code by uiwait, you could finish the code here and insert the code for the processing in the callback of the button.
clf is tricky, because it cleans the current figure. This might be evil, if you work with multiple figure and kill another GUI. Better use the figure handle to be sure to clean the wanted figure.
function [dp,th,sp]=clbk(src,evd)
clf
clearvars th sp Lz gk
clearvars is completely useless here: It clear the variables in the current workspace. Each function has its own workspace (set of local variables), an these variables do not exist in the function clbk. After clearing them, exporting them as output is double invalid: 1. callbacks do not have outputs, 2. thevariables have been removed before, so there is nothing to export.
Avoid working with scripts instead. Convert Drilling_Problem_Fig.m to a function, then its workspace is clean automatically.
Calling Drilling_Problem_Fcn() inside Drilling_Problem_Fig is not meaning full, as far as I can see. Or at least I'm confused, because both functions are calling each other mutually.
Start with converting Drilling_Problem_Fig (which looks more like a kind of "Fcn" code, in opposite to the "_Fcn" function, which looks more like a GUI code?) to a function with the inputs dp and the outputs th and sp. Then try to insert the calls into the callback of the figure. If there are still problems afterwards, come back an post the new code and ask concerning questions.
