#include <juce_Timer.h>
Public Member Functions | |
virtual | ~Timer () |
virtual void | timerCallback ()=0 |
void | startTimer (int intervalInMilliseconds) noexcept |
void | startTimerHz (int timerFrequencyHz) noexcept |
void | stopTimer () noexcept |
bool | isTimerRunning () const noexcept |
int | getTimerInterval () const noexcept |
Static Public Member Functions | |
static void JUCE_CALLTYPE | callAfterDelay (int milliseconds, std::function< void()> functionToCall) |
static void JUCE_CALLTYPE | callPendingTimersSynchronously () |
Protected Member Functions | |
Timer () noexcept | |
Timer (const Timer &) noexcept | |
Makes repeated callbacks to a virtual method at a specified time interval.
A Timer's timerCallback() method will be repeatedly called at a given interval. When you create a Timer object, it will do nothing until the startTimer() method is called, which will cause the message thread to start making callbacks at the specified interval, until stopTimer() is called or the object is deleted.
The time interval isn't guaranteed to be precise to any more than maybe 10-20ms, and the intervals may end up being much longer than requested if the system is busy. Because the callbacks are made by the main message thread, anything that blocks the message queue for a period of time will also prevent any timers from running until it can carry on.
If you need to have a single callback that is shared by multiple timers with different frequencies, then the MultiTimer class allows you to do that - its structure is very similar to the Timer class, but contains multiple timers internally, each one identified by an ID number.
Definition at line 51 of file juce_Timer.h.
|
protectednoexcept |
Creates a Timer. When created, the timer is stopped, so use startTimer() to get it going.
Definition at line 293 of file juce_Timer.cpp.
Referenced by Timer().
|
protectednoexcept |
Creates a copy of another timer.
Note that this timer won't be started, even if the one you're copying is running.
Definition at line 294 of file juce_Timer.cpp.
|
virtual |
Destructor.
Definition at line 296 of file juce_Timer.cpp.
|
static |
Invokes a lambda after a given number of milliseconds.
Definition at line 372 of file juce_Timer.cpp.
|
static |
For internal use only: invokes any timers that need callbacks. Don't call this unless you really know what you're doing!
Definition at line 341 of file juce_Timer.cpp.
|
inlinenoexcept |
Returns the timer's interval.
Definition at line 116 of file juce_Timer.h.
|
inlinenoexcept |
Returns true if the timer is currently running.
Definition at line 111 of file juce_Timer.h.
Referenced by isTimerRunning(), and ~Timer().
|
noexcept |
Starts the timer and sets the length of interval required.
If the timer is already started, this will reset it, so the time between calling this method and the next timer callback will not be less than the interval length passed in.
intervalInMilliseconds | the interval to use (any value less than 1 will be rounded up to 1) |
Definition at line 309 of file juce_Timer.cpp.
Referenced by juce::PropertiesFile::propertyChanged(), juce::MultiTimer::startTimer(), startTimerHz(), and timerCallback().
|
noexcept |
Starts the timer with an interval specified in Hertz. This is effectively the same as calling startTimer (1000 / timerFrequencyHz).
Definition at line 324 of file juce_Timer.cpp.
Referenced by timerCallback().
|
noexcept |
Stops the timer.
No more timer callbacks will be triggered after this method returns.
Note that if you call this from a background thread while the message-thread is already in the middle of your callback, then this method will cancel any future timer callbacks, but it will return without waiting for the current one to finish. The current callback will continue, possibly still running some of your timer code after this method has returned.
Definition at line 332 of file juce_Timer.cpp.
Referenced by juce::PropertiesFile::save(), startTimerHz(), timerCallback(), and ~Timer().
|
pure virtual |
The user-defined callback routine that actually gets called periodically.
It's perfectly ok to call startTimer() or stopTimer() from within this callback to change the subsequent intervals.