Hi LEMF,
The behaviour you are experiencing is due to the “SetObservable” property triggering its listener callback immediately upon assignment, which can indeed interrupt the flow of the initial callback function. To overcome this, you can set the “BusyAction” property to “queue” as this tells MATLAB to execute the interrupting callback after the running callback finishes. The “Interruptible” property will be set to “off”.
Alternatively, you can also defer the execution of the property change that triggers the listener by using a timer or by scheduling the change to occur after the current callback finishes its critical section. Here is a simple example using a timer:
% Inside your dropdown callback
function dropdownCallback(app, event)
% Your initial callback code here
% Defer the property assignment
t = timer;
t.StartDelay = 0.01; % Delay in seconds, adjust as needed
t.TimerFcn = @(~,~) setProperty(app);
start(t);
end
% Separate function to change the property
function setProperty(app)
app.YourObservableProperty = newValue; % YourObservableProperty is your property
end
You can refer to the following documentation to know more about functions used:
- Interrupt Callback Execution: https://www.mathworks.com/help/matlab/creating_guis/interrupt-callback-execution.html
- Timer: https://www.mathworks.com/help/matlab/ref/timer.html
Best Regards,
Abhishek Chakram
