Difference between revisions of "Oolite JavaScript Reference: Timer"
(Moving Oolite JS reference into a subcategory of Oolite scripting.) |
|||
Line 97: | Line 97: | ||
'''N.B.:''' as of Oolite 1.74, timers will be removed automatically by Oolite when the 'this' object goes out of scope, without the need to use any of these examples. |
'''N.B.:''' as of Oolite 1.74, timers will be removed automatically by Oolite when the 'this' object goes out of scope, without the need to use any of these examples. |
||
− | [[Category:Oolite |
+ | [[Category:Oolite JavaScript reference]] |
Revision as of 14:59, 19 June 2010
Prototype: Object
Subtypes: none
This class was added in Oolite test release 1.70.
Timer objects are used to perform tasks after a delay or on a repeating schedule. When a timer is created, it is given a function to call, and a delay and an optional interval in seconds in game real time. The next fire time of the timer is set to the current time + the delay. When the game clock reaches (or passes) the next fire time, the function is called. If the timer has a positive interval, the interval is added to the next fire time. Otherwise, the timer stops.
Note: in order for a timer to work consistently, you must keep a reference to it as long as it is in use. The easiest way is to make it a property of your script: this.timer = new Timer(this, this.doSomething, 5, 5)
. If this is not done, the JavaScript runtime may delete the timer at any time to free up memory.
N.B.: Before 1.74, timers associated with ship scripts did not stop when the ship itself died. If scripting for Oolite 1.73.4 or earlier, either the timer is deleted inside the ship's this.shipDied, or a check for the existence of the ship must be placed inside the timer itself, as in the timers examples at the bottom of this page. Timers run independent of the script and are not deleted with a ship script. When the timer is not stopped and uses a property of a removed ship script, it can crash Oolite.
Contents
Constructor
new Timer(this : Object, function : Function, delay : Number [, interval : Number]) : Timer
Creates a new timer which will call function
after delay
seconds, and optionally repeatedly every interval
seconds. If delay
is zero or more, the timer will be started automatically. If interval
is 0 or less, the timer will not repeat. If interval
is greater than 0 but less than 0.25, it will be rounded up to 0.25.
N.B.: as of Oolite 1.74, if the first parameter ('this : Object') goes out of scope (usually because the ship attached to the 'this' object is destroyed, or left behind when the player executes a hyperspace jump), the timer will now be stopped and removed automatically.
Properties
interval
interval : Number (read/write)
The rate at which the timer repeats. For a one-shot timer, this will be -1. If set to 0 or a negative number, it will be treated as -1. If set to a number between 0 and 0.25, it will be rounded up to 0.25.
isPersistent
This property is deprecated and will be removed in Oolite test release 1.74.
isPersistent : Boolean (read/write)
A persistent timer will continue to run when the game resets (i.e., the player dies or loads a new game). A non-persistent timer will be stopped when the game is reset (but can be restarted using start()
). Timers are not persistent by default.
isRunning
isRunning : Boolean (read-only)
true
if the timer is running, false
if it is stopped.
nextTime
nextTime : Number (read/write when stopped)
The next time the timer will fire, if it is running at that time. This can be modified if the timer is stopped. Note that this is an absolute time, not a delay. You can get the current absolute time using clock.absoluteSeconds
.
Methods
start
function start() : Boolean
Starts the timer, if it is not currently running. This will fail if it is a one-shot timer (i.e., its interval
is -1) and its nextTime
is in the past. Returns true
if successful or the timer was already running, false
on failure (i.e., the same as isRunning
after start()
is called).
stop
function stop()
Stops the timer, if it is currently running.
Examples
Timer connected to ship. When the ship dies or when the player leaves the system, its timer is removed.
this.shipSpawned = function () { this.shipTimer = new Timer(this, this.testTimer, 10, 10); delete this.shipSpawned; }; this.shipDied = function () { if (this.shipTimer) { this.shipTimer.stop(); delete this.shipTimer; } // other shipDied actions. ... }; this.playerWillEnterWitchspace = function () { if (this.shipTimer) { this.shipTimer.stop(); delete this.shipTimer; } ... }; this.testTimer = function () { // main timer code. ... };
Timer connected to ship. The timer itself keeps track of the ship it's attached to, and removes itself when necessary.
this.shipSpawned = function () { this.shipTimer = new Timer(this, this.testTimer, 10, 10); delete this.shipSpawned; }; this.testTimer = function () { // stop the timer if its associated ship doesn't exist anymore if (!this.ship || !this.ship.isValid) { log(this.name, "ERROR detected; Timer fired but this.ship is undefined"); if (this.shipTimer) { this.shipTimer.stop(); delete this.shipTimer; } return; } // main timer code. ... };
N.B.: as of Oolite 1.74, timers will be removed automatically by Oolite when the 'this' object goes out of scope, without the need to use any of these examples.