class TimerPort
|
synchronized millisecond timing for service threads.
More... |
|
|
Public Members
Protected Members
Detailed Description
Timer ports are used to provide synchronized timing events when managed
under a "service thread" such as SocketService. This is made into a
stand-alone base class since other APE derived libraries (such as the
APE serial handlers) may also use the pooled "service thread" model
and hence also require this code for managing timing.
[protected]
Create a timer, mark it as inactive, and set the initial
"start" time to the creation time of the timer object. This
allows "incTimer" to initially refer to time delays relative
to the original start time of the object.
Set a new start time for the object based on when this call is
made and optionally activate the timer for a specified number
of milliseconds. This can be used to set the starting time
of a realtime session.
Parameters:
timeout | delay in milliseconds from "now"
|
Set a timeout based on the current time reference value either
from object creation or the last setTimer(). This reference
can be used to time synchronize realtime data over specified
intervals and force expiration when a new frame should be
released in a synchronized manner.
Parameters:
timeout | delay in milliseconds from reference.
|
This is used to "disable" the service thread from expiring
the timer object. It does not effect the reference time from
either creation or a setTimer().
This is used by service threads to determine how much time
remains before the timer expires based on a timeout specified
in setTimer() or incTimer(). It can also be called after
setting a timeout with incTimer() to see if the current timeout
has already expired and hence that the application is already
delayed and should skip frame(s).
return time remaining in milliseconds, or -1 if inactive.
- Author: David Sugar <dyfet@ostel.com>
- Generated: dyfet@home.sys on Tue Mar 7 09:18:03 200.