There is an implicit behavior where calls to Matlab functions with no output arguments are non-blocking, and calls to Matlab functions witth output arguments are blocking.
This is in general fine but some functions with no output arguments are meant to be blocking (eg, functions that asks for user some input or to show a visualization for user to check). Currently, the only way to make such a call blocking is to change the Matlab function to return an argument.
Adding an optional argument to run_func() such as blocking=True that would make the call blocking in any case regardless of output arguments would solve this issue.
There is an implicit behavior where calls to Matlab functions with no output arguments are non-blocking, and calls to Matlab functions witth output arguments are blocking.
This is in general fine but some functions with no output arguments are meant to be blocking (eg, functions that asks for user some input or to show a visualization for user to check). Currently, the only way to make such a call blocking is to change the Matlab function to return an argument.
Adding an optional argument to
run_func()such asblocking=Truethat would make the call blocking in any case regardless of output arguments would solve this issue.