How can I interrupt a callback and NOT come back to finish its execution in MATLAB?
68 views (last 30 days)
MathWorks Support Team on 27 Jun 2009
I have a GUI with a callback. When the callback is interrupted during a loop, the interrupting function executes and then MATLAB returns to finish the execution of the interrupted callback. I would like MATLAB to exit the original loop once the interrupting function has finished executing.
I have tried setting the 'Interruptible' and 'BusyAction' properties of the UICONTROL to all different combinations, and nothing seemed to help.
For example, in the attached file 'testinterrupt', after entering the 1st loop, if I press the pushbutton again, MATLAB will enter loop 2, but return and finish loop 1 after loop 2 is done executing.
MathWorks Support Team on 8 May 2020
Edited: MathWorks Support Team on 8 May 2020
The ability to have the interrupted function stop executing after the interrupting function is completed is not automatically available in MATLAB.
However, it is possible, as shown in the attached example "interrupt_stop", to code this logic into the loop. Notice the callback structure for PushButton1:
Inside the FOR loop, once the callback is interrupted, the function will execute completely, and then return to where it left inside the FOR loop. Eventually it will reach the IF statement with a TRUE condition, which will trigger the execution of the RETURN command, and therefore stop the execution of the original callback.
In this example, the functions SETAPPDATA and GETAPPDATA are used. These functions allow for the creation of user-defined properties, in this case "Callbackrun".
Example is now included. Please note this question is intended for the R2006b release of MATLAB and the example might not work in newer releases.* If you are still having an issue with callbacks, please try MATLAB App Designer (the replacement for GUIDE), or contact MathWorks technical support. *
More Answers (1)
tommsch on 23 Nov 2020
I think I found a solution. See my proof-of-concept submission errorat at the Matlab Fileexchange. A similar approach should be possible with the use of callbacks. Since I never used callbacks before, I cannot tell you more, but I am strongly convinced it is possible.
errorat injects a call to clear all in every line of a function - thus, making it very likely that the function will crash.