Hi Brian,
I understand that you are trying to modify the audioplayer timer so that it acts like a timer with "BusyMode" set to 'drop'. You have rightly concluded that the "audioplayer" class does not directly let you set the "BusyMode" property for the timer. However, you can modify your "TimerFcn" such that it behaves like a timer with BusyMode='drop'. The modified code for "TimerFcn" is as follows:
function TimerFcn(src, ~)
persistent lastExecTime;
if isempty(lastExecTime)
lastExecTime = tic; % Initialize the timer
end
currentTime = toc(lastExecTime);
clickIntervalWithDelay = src.UserData.clickInterval + extraDelay;
% Check if the elapsed time since the last execution is less than the
% desired interval plus the extra delay. If so, skip the current callback.
if currentTime < clickIntervalWithDelay
return;
end
% If the function is executing, reset the last execution time.
lastExecTime = tic;
% Issue a notification to the console that TimerFcn has been called
src.UserData.clickCount = src.UserData.clickCount + 1;
fprintf('click: %d\n', src.UserData.clickCount);
% Simulate the processing delay
pause(extraDelay);
end
The notable changes made in the code are as follows:
- Used a persistent variable called "lastExecTime" to keep track of the time when last callback was executed.
- If the elapsed time is less than the sum of "clickInterval" and "extraDelay", the function returns immediately. So, the callback is dropped.
- If enough time has passed then the "lastExecTime" is reset.
This way you can simulate the functionality of the dropped callback. You need to keep a few things in consideration before executing this piece of code. If the "TimerFcn" is called repeatedly in rapid succession, then it may cause the "lastExecTime" to not update properly.
Also, using "pause" function within the callback can make the UI unresponsive. Consider using non-blocking methods to handle GUI updates like asynchronous operation or using a dedicated thread.
I hope it helps.
