Stop an app designer callback thread like the debugger does?
3 次查看(过去 30 天)
显示 更早的评论
It is evident that whenever the user clicks a button in an app designer app, the callback is called in a new thread. The debugger takes advantage of this, the red "stop" square button obviously terminates the currently running callback thread. Very clean, very effective.
Now, is there any way that I as a programmer can do the same thing? Here's my problem. I'm building a scientific analysis program, and the users have a lot of options. The wrong options combined with the wrong data can produce a VERY long-running computation, and the user has no good way of getting out of it. Indeed, my users are tending to click extra buttons, setting yet more computations in motion, and it ends up in a meltdown.
So, can I kill the thread, or do I just have to put checkpoints in all my long-running code and check for a stop variable?
0 个评论
回答(1 个)
Walter Roberson
2024-4-21
"It is evident that whenever the user clicks a button in an app designer app, the callback is called in a new thread."
No, the current thread is interrupted, pushing the location onto the stack, and the callback is run in the same thread. At the end of execution of the callback, the old information is popped and execution is resumed.
The entire execution is on a single thread, unless background pool is used or unless one of the facilities of the Parallel Computing Toolbox are used. (Well, graphics runs on a seperate thread.)
(The single thread used is distinct from threads that manage the user interface.)
8 个评论
Andres
2024-4-23
Okay, but hitting "the red 'stop' square button", as the OP suggests, would have similar limitations (at least), wouldn't it?
Walter Roberson
2024-4-23
Yes, hitting the Stop button has the limitation that it does not stop until the next line of MATLAB code.
另请参阅
类别
在 Help Center 和 File Exchange 中查找有关 Environment and Settings 的更多信息
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!