Programming

Handling Callback Function Queuing Conflicts

At busy times, in multiple-execution scenarios, the timer may need to add the timer callback function (TimerFcn) to the MATLAB execution queue before the previously queued execution of the callback function has completed. You can determine how the timer object handles this scenario by using the BusyMode property.

If you specify 'drop' as the value of the BusyMode property, the timer object skips the execution of the timer function callback if the previously scheduled callback function has not already completed.

If you specify 'queue', the timer object waits until the currently executing callback function finishes before queuing the next execution of the timer callback function.

Note    In 'queue' mode, the timer object tries to make the average time between executions equal the amount of time specified in the Period property. If the timer object has to wait longer than the time specified in the Period property between executions of the timer function callback, it shortens the time period for subsequent executions to make up the time.

If the BusyMode property is set to 'error', the timer object stops and executes the timer object error callback function (ErrorFcn), if one is specified.

Executing a Timer Callback Function Multiple Times

Deleting Timer Objects from Memory

© 1994-2005 The MathWorks, Inc.