Configure a callback in App Designer to be non-interruptable

9 views (last 30 days)
I'm using USB connected Arduino device and have the following line:
configureCallback(app.PicoCom,"terminator",@app.PicoInput);
The function app.PicoInput does it's job, but I would like it to complete before going back to the main program. If a function has a component that calls it then the function will be the "callback area" of the app and the component has callback execution control. Since this function is called by an interrupt and is set up by startupFcn(app) it doesn't have a component. How can I make it non-interruptable without messing with flags and mutex?

Accepted Answer

Walter Roberson
Walter Roberson on 18 Jul 2025
The secrets to making a function uninterruptible is:
  • write the code all on one line. MATLAB checks for interrupts at the beginning of each line of code, so if you write it all on one line then there will be no opportunity to interrupt
  • write the code entirely in terms of built-in functions. You might have prevented interrupts by writing all on one line, but if what you are calling is MATLAB code that was written on multiple lines then MATLAB will be checking for interrupts at the beginning of those lines.
  • do not call pause() or uifigure() or figure() or uiwait() or waitfor() or drawnow()
  5 Comments
Gavin
Gavin 8 minutes ago
app.status is initialized during startup and well managed.
Data typing is handled in the code, structures are initialized as needed.
e.g.
function InitInBuffer(app)
% Clean out InBuffer reset pointers
app.InBuffer = zeros(40, 2); % Circular Array init
app.InPtr = 1; % Where to read
app.OutPtr = 1; % Where Pico Data goes
app.BFEmpty = true; % No data yet
end
The circular buffer is handled correctly.I use it to get data out of the Windows USB buffer where I can deal with in in my own time. Type isn't changed to a char until it's read from the buffer.
Typ = char(app.InBuffer(app.OutPtr,1));
if ~isletter(Typ) % manage possible error (it never happens)
And BTW the PicoInput code is about 80 lines so not going to fit on one line.
Hasn't been a problem any more with ML2025
Walter Roberson
Walter Roberson about 2 hours ago
function InitInBuffer(app)
% Clean out InBuffer reset pointers
app.InBuffer = zeros(40, 2); % Circular Array init
You are not returning app from the function, and app is not a global variable or a shared variable. All changes to app will be lost when the funtion returns.

Sign in to comment.

More Answers (0)

Categories

Find more on Dialog Boxes in Help Center and File Exchange

Products


Release

R2024b

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!