Using one button to cycle through three different commands

As the title suggests, I was wondering if there was a way for me to have one button (just a regular old pushbutton from a hobby shop) cycle through commands each time it is pressed. I press it once it does one command, press it again it executes the second command, press it a third time it does the third command, then once it reaches the end of the list it does the first command again.

Would I just use the ButtonStateChange as stated here? http://arduino.cc/en/Tutorial/ButtonStateChange

/*
  State change detection (edge detection)

 Often, you don't need to know the state of a digital input all the time,
 but you just need to know when the input changes from one state to another.
 For example, you want to know when a button goes from OFF to ON.  This is called
 state change detection, or edge detection.

 This example shows how to detect when a button or button changes from off to on
 and on to off.

 The circuit:
 * pushbutton attached to pin 2 from +5V
 * 10K resistor attached to pin 2 from ground
 * LED attached from pin 13 to ground (or use the built-in LED on
   most Arduino boards)

 created  27 Sep 2005
 modified 30 Aug 2011
 by Tom Igoe

This example code is in the public domain.

 http://arduino.cc/en/Tutorial/ButtonStateChange

 */

// this constant won't change:
const int  buttonPin = 2;    // the pin that the pushbutton is attached to
const int ledPin = 13;       // the pin that the LED is attached to

// Variables will change:
int buttonPushCounter = 0;   // counter for the number of button presses
int buttonState = 0;         // current state of the button
int lastButtonState = 0;     // previous state of the button

void setup() {
  // initialize the button pin as a input:
  pinMode(buttonPin, INPUT);
  // initialize the LED as an output:
  pinMode(ledPin, OUTPUT);
  // initialize serial communication:
  Serial.begin(9600);
}


void loop() {
  // read the pushbutton input pin:
  buttonState = digitalRead(buttonPin);

  // compare the buttonState to its previous state
  if (buttonState != lastButtonState) {
    // if the state has changed, increment the counter
    if (buttonState == HIGH) {
      // if the current state is HIGH then the button
      // wend from off to on:
      buttonPushCounter++;
      Serial.println("on");
      Serial.print("number of button pushes:  ");
      Serial.println(buttonPushCounter);
    } 
    else {
      // if the current state is LOW then the button
      // wend from on to off:
      Serial.println("off"); 
    }
  }
  // save the current state as the last state, 
  //for next time through the loop
  lastButtonState = buttonState;

  
  // turns on the LED every four button pushes by 
  // checking the modulo of the button push counter.
  // the modulo function gives you the remainder of 
  // the division of two numbers:
  if (buttonPushCounter % 4 == 0) {
    digitalWrite(ledPin, HIGH);
  } else {
   digitalWrite(ledPin, LOW);
  }
  
}

Or is there something else? I really need help with this as I am trying to get this project going and I have everything else working but this one button which needs to cycle through three commands.

Thanks in advanced!

M...

I looks to be more a programming problem than a multiplexing one… Anyway yes, you can use 90% of the code example. Replace the modulo test with something more specific to your project. A list containing the functions as items to call with "pushbuttoncounter" as the corresponding index.

Also, be aware of bouncing buttons (they all do). In this sketch you are checking for the button to change state, a few thousand times a second. I'd be very impressed if you could press the button so that the press will be only seen in one iteration. Do a search on "debounce", which often is checking the state of that button multiple times, to be sure it isn't changing state again where you were actually pressing it once.

Then count the number of registered button presses. If you count more than 3 presses, reset your counter to 1. Then set up your sketch in such way that this counter decides what is done and what is skipped. It's really not that difficult, but you need to keep focusing on what you need to do depending on the counter, and what has to be done every iteration.