I'm creating a content rotator in jQuery. 5 items total. Item 1 fades in, pauses 10 seconds, fades out, then item 2 fades in. Repeat.

Simple enough. Using setTimeout I can call a set of functions that create a loop and will repeat the process indefinitely.

I now want to add the ability to interrupt this rotator at any time by clicking on a navigation element to jump directly to one of the content items.

I originally started going down the path of pinging a variable constantly (say every half second) that would check to see if a navigation element was clicked and, if so, abandon the loop, then restart the loop based on the item that was clicked.

The challenge I ran into was how to actually ping a variable via a timer. The solution is to dive into JavaScript closures...which are a little over my head but definitely something I need to delve into more.

However, in the process of that, I came up with an alternative option that actually seems to be better performance-wise (theoretically, at least). I have a sample running here:

http://jsbin.com/uxupi/14

(It's using console.log so have fireBug running)

Sample script:

$(document).ready(function(){

var loopCount = 0;

$('p#hello').click(function(){
  loopCount++;
  doThatThing(loopCount);
})

function doThatOtherThing(currentLoopCount) {  
console.log('doThatOtherThing-'+currentLoopCount);
if(currentLoopCount==loopCount){
  setTimeout(function(){doThatThing(currentLoopCount)},5000)
 }
}  


function doThatThing(currentLoopCount) {
 console.log('doThatThing-'+currentLoopCount);
 if(currentLoopCount==loopCount){
   setTimeout(function(){doThatOtherThing(currentLoopCount)},5000);
 }
}

}) 

The logic being that every click of the trigger element will kick off the loop passing into itself a variable equal to the current value of the global variable. That variable gets passed back and forth between the functions in the loop.

Each click of the trigger also increments the global variable so that subsequent calls of the loop have a unique local variable.

Then, within the loop, before the next step of each loop is called, it checks to see if the variable it has still matches the global variable. If not, it knows that a new loop has already been activated so it just ends the existing loop.

Thoughts on this? Valid solution? Better options? Caveats? Dangers?

UPDATE:

I'm using John's suggestion below via the clearTimeout option.

However, I can't quite get it to work. The logic is as such:

var slideNumber = 0; 

var timeout = null;


    function startLoop(slideNumber) {
        ...do stuff here to set up the slide based on slideNumber...
        slideFadeIn()
    }

function continueCheck(){
    if (timeout != null) {
        // cancel the scheduled task.
        clearTimeout(timeout);
        timeout = null;
        return false;
    }else{
        return true;
    }
};

function slideFadeIn() {
    if (continueCheck){
    // a new loop hasn't been called yet so proceed...

    // fade in the LI
    $currentListItem.fadeIn(fade, function() {
        if(multipleFeatures){
            timeout = setTimeout(slideFadeOut,display);
        }
    });         
};


function slideFadeOut() {
        if (continueLoop){
        // a new loop hasn't been called yet so proceed...  
        slideNumber=slideNumber+1;

        if(slideNumber==features.length) {
            slideNumber = 0;
        };
        timeout = setTimeout(function(){startLoop(slideNumber)},100);
};


startLoop(slideNumber);

The above kicks of the looping.

I then have navigation items that, when clicked, I want the above loop to stop, then restart with a new beginning slide:

$(myNav).click(function(){
    clearTimeout(timeout);
    timeout = null;
    startLoop(thisItem);
})

If I comment out 'startLoop...' from the click event, it, indeed, stops the initial loop. However, if I leave that last line in, it doesn't actually stop the initial loop. Why? What happens is that both loops seem to run in parallel for a period.

So, when I click my navigation, clearTimeout is called, which clears it.