In App Designed app: When does a function called within another function spawn a new thread?
I’m having SO much trouble! I think maybe when I call a function from within another function or callback it’s going into a new thread.
I want it to finish the function before moving on. Is the best way to do that to make the function return a (dummy) value?
Since there is nothing to return but completion do I need to declare
function finish = MyFunction(app);
does finish need a value assigned at the end?
or just short cut and call
fin = MyFunction %#ok suppress mLint about unused return value?I’m having SO much trouble! I think maybe when I call a function from within another function or callback it’s going into a new thread.
I want it to finish the function before moving on. Is the best way to do that to make the function return a (dummy) value?
Since there is nothing to return but completion do I need to declare
function finish = MyFunction(app);
does finish need a value assigned at the end?
or just short cut and call
fin = MyFunction %#ok suppress mLint about unused return value? I’m having SO much trouble! I think maybe when I call a function from within another function or callback it’s going into a new thread.
I want it to finish the function before moving on. Is the best way to do that to make the function return a (dummy) value?
Since there is nothing to return but completion do I need to declare
function finish = MyFunction(app);
does finish need a value assigned at the end?
or just short cut and call
fin = MyFunction %#ok suppress mLint about unused return value? threads, function calls MATLAB Answers — New Questions