Look more closely at these methods..

// --- >8 snip
	public function go() : Void {
		if(!running) {
			running = true;
			setTimeout();
		} else {
			restart();
		}
	}

	private function setTimeout () : Void {
		timerInterval = setInterval (Delegate.create(this, timeoutComplete), duration);
	}

	public function restart (newDuration : Number) : Void {
		if(newDuration != undefined) {
			duration = newDuration;
		}
		dispose();
		go();
	}
// --- >8 snip

go() doesn’t run setTimeout() unconditionally, also setTimeout is a private method. The public methods are the constructor, go(), restart() and dispose() (and it’s aliases, crush, kill, destroy ;-) )

I hope this addresses your potential bug, if I’m on the wrong track, could you explain the circumstances under which the bug could arise. Cheers.

private function setTimeout () : Void {
clearInterval(timerInterval);
timerInterval = setInterval (Delegate.create(this, timeoutComplete), duration);
}

If you need to do something quick and dirty then it’s always ok to use whatever method you like, however, when you develop larger systems in Flash using AS2.0 it is (very often) beneficial in the long run to design your application along the lines of an event based model.

As an aside, I’ve been looking closely at the NSNotificationCenter which has been implemented in the ASAPFramework and also in ActionStep, this is a very cool event model which allows objects to listen for messages for which they don’t neccessarily know the broadcaster.

Some more info about Notifications.

The thing is many people have yet to upgrade to Flash 8, (sad as that may be.) And so the class uses setInterval instead of setTimeout.

So this is for maximum compatibility in AS2.0.

function calledOnlyOnce(Void):Void {
trace(’I was called once’);
}

setTimeout(this, ‘calledOnlyOnce’, 1000);