#include <timer.h>
Inheritance diagram for PTimer:
Public Member Functions | |
Construction | |
PTimer (long milliseconds=0, int seconds=0, int minutes=0, int hours=0, int days=0) | |
PTimer (const PTimeInterval &time) | |
PTimer & | operator= (DWORD milliseconds) |
PTimer & | operator= (const PTimeInterval &time) |
virtual | ~PTimer () |
Control functions | |
virtual void | SetInterval (PInt64 milliseconds=0, long seconds=0, long minutes=0, long hours=0, int days=0) |
void | RunContinuous (const PTimeInterval &time) |
void | Stop () |
BOOL | IsRunning () const |
void | Pause () |
void | Resume () |
BOOL | IsPaused () const |
void | Reset () |
const PTimeInterval & | GetResetTime () const |
Notification functions | |
virtual void | OnTimeout () |
const PNotifier & | GetNotifier () const |
void | SetNotifier (const PNotifier &func) |
Static Public Member Functions | |
Global real time functions | |
PTimeInterval | Tick () |
unsigned | Resolution () |
A timer on completion calls the virtual function OnTimeout()#. This will in turn call the callback function provided by the instance. The user may either override the virtual function or set a callback as desired.
A list of active timers is maintained by the applications PProcess# instance and the timeout functions are executed in the context of a single thread of execution. There are many consequences of this: only one timeout function can be executed at a time and thus a user should not execute a lot of code in the timeout call-back functions or it will dealy the timely execution of other timers call-back functions.
Also timers are not very accurate in sub-second delays, even though you can set the timer in milliseconds, its accuracy is only to -0/+250 ms. Even more (potentially MUCH more) if there are delays in the user call-back functions.
Another trap is you cannot destroy a timer in its own call-back. There is code to cause an assert if you try but it is very easy to accidentally do this when you delete an object that contains an onject that contains the timer!
Finally static timers cause race conditions on start up and termination and should be avoided.
|
Create a new timer object and start it in one shot mode for the specified amount of time. If the time was zero milliseconds then the timer is { not} started, ie the callback function is not executed immediately.
|
|
|
|
Destroy the timer object, removing it from the applications timer list if it was running. |
|
Get the current call back function that is called whenever the timer expires. This is called by the OnTimeout()# function.
|
|
Get the time this timer was set to initially. |
|
Determine if the timer is currently paused.
|
|
Determine if the timer is currently running. This really is only useful for one shot timers as repeating timers are always running.
|
|
This function is called on time out. That is when the system timer processing decrements the timer from a positive value to less than or equal to zero. The interval is then reset to zero and the function called. Please note that the application should not execute large amounts of code in this call back or the accuracy of ALL timers can be severely impacted. The default behaviour of this function is to call the PNotifier# callback function. |
|
|
|
Restart the timer in one shot mode using the specified time value. If the timer was already running, the "time left" is simply reset.
|
|
Pause a running timer. This differs from the Stop()# function in that the timer may be resumed at the point that it left off. That is time is "frozen" while the timer is paused. |
|
Restart a timer continuing from the time it was initially. |
|
Get the smallest number of milliseconds that the timer can be set to. All actual timing events will be rounded up to the next value. This is typically the platforms internal timing units used in the Tick()# function.
|
|
Restart a paused timer continuing at the time it was paused. The time left at the moment the timer was paused is the time until the next call to the notification function. |
|
Start a timer in continous cycle mode. Whenever the timer runs out it is automatically reset to the time specified. Thus, it calls the notification function every time interval. |
|
Set the value of the time interval. The time interval, in milliseconds, is the sum of all of the parameters. For example all of the following are equivalent: {verbatim} SetInterval(120000) SetInterval(60000, 60) SetInterval(60000, 0, 1) SetInterval(0, 60, 1) SetInterval(0, 0, 2) {verbatim}
Reimplemented from PTimeInterval. |
|
Set the call back function that is called whenever the timer expires. This is called by the OnTimeout()# function. |
|
Stop a running timer. The imer will not call the notification function and is reset back to the original timer value. Thus when the timer is restarted it begins again from the beginning. |
|
Get the number of milliseconds since some arbtrary point in time. This is a platform dependent function that yields a real time counter. Note that even though this function returns milliseconds, the value may jump in minimum quanta according the platforms timer system, eg under MS-DOS and MS-Windows the values jump by 55 every 55 milliseconds. The Resolution()# function may be used to determine what the minimum time interval is.
|